Update February 18, 2015:
This is getting interesting. I suddenly thought maybe Chrome allows parameters to be passed and indeed there are, tons of it. Here are the switches:
http://peter.sh/experiments/chromium-command-line-switches/
As for forcing Chrome to open on a new window instead of the existing one as a tab, it is
--new-window
I also updated the sample below to know whether the operation is successful or not so it won't accidentally open any other active window aside from our target.
Later:
As for my problem to get rid of Chrome's internal titlebar, the trick came out to be very easy. All we need to do is move the chrome up from within our form that its own internal titlebar cannot be seen anymore, and thus rendering it likewise immovable.
Check the codes below, adjust lnMove value based on how you set up your Chrome on your end. Since in mine I show my bookmarks, then my adjustment is 100. Maybe on the link I gave above on the command switches, there are commands to hide those, but I did not check anymore. :)
======
Sparked by last week's thread inside Foxite Forum about placing an IE Browser inside VFP Form, I thought to myself it would be cool to put
Google Chrome inside our form for a change.
Also, this will ensure that most probably a webpage can be displayed properly being Chrome is always up to date with changes introduced now and then, as compared to IE that has been left far behind and is giving developers now some headache to fix it via Registry tweaks.
Googling does not give me any result on how this new sudden thought of mine can be done as I never found any that shows how to achieve this without downloading and working on extension designed to provide automation to google. But I simply wanted chrome to be inside our VFP form using stock VFP commands and function plus utilizing WinAPIs.