Follow-Up Chrome Games: Google to Lock Your Mouse
It's not just about a joystick. It's about your mouse as well.
Last month, I wrote about Google's aggressive strategy to fine tune Chrome as a gaming interface that will run future HTML5 as well as traditional C++-based games. The Chromium revision log is a treasure trove for those who want to follow Google's activities in this space, but my attention was specifically caught by a proposal to lock your mouse cursor.
Developer Vincent Scheib posted an early version of the "Mouse lock specification draft" this week, which essentially offers web app developers a possibility to lock or hide a mouse cursor in their applications - or position it in a preset, hidden location. The purpose is to remove the mouse cursor as a distracting element from the screen, but keep the mouse as a content controlling device in place - for example to navigate within a 3D environment. Scheib said that the draft is in the process of being adopted in the W3 Webevents Working Group.
The proposal should be seen in connection with an effort to enable a wider array of input devices via the Joystick API as well as Google's continued efforts to push HTML5 game development. Chrome is not just a browser interface anymore, but has moved to become an application interface that is shaping up to become a compelling game environment. It is worth watching what Google is cooking.

What are you talking about?
What are you talking about?
I agree, my only problem is the way they compared the empire state building to how single mum's bring up their children wasn't ethical - perhaps they could change this in the next patch.
Me!
I think not! I rather enjoy reading the foolish comments of know it all's who just read the title and try to comment on the articles as seen below.
I can't help but chuckle at this nonsensical comment or at the posters expense. We should also not thumb them down, we should thumb them up! Just like how we cheer on the idiot about to do something incredibly stupid that will no doubt end in failure and pain. We get a good laugh, they are too stupid to learn anything. Everybody wins!
That's what this is about. Now go back to your conspiracy theories.
Idiots. One and all.
Boy I was confused for the first 3 comments and I'm still sober!
I had to come read this story just to stop me from wondering what it was about.
i play almost every game windowed now, and i have to say, every game i have that is correctly coded has a way for the mouse to unlock without a ctrl+tab
now i can see an ad or someone being a completed douche programming an as/page that locks the mouse, and has no interrupt so you have to go to a basic os function, such as ctrl+tab alt+ctrl+esc or ctrl+alt+delete (one of them may be wrong, as i haven't had to uses it sense win 98)
now the point is, they are adding mouse locking, without forcing a standard way to unlock...
picture this.
a program that acts like a virus, executes itself and deletes everything that isnt locked by the os or even os critical things that just arent locked, and are mostly unnecessary for boot up.
most people who know tech could get out of that fast enough to stop any real damage, but people who don't? imagine if the program had a game attached, to distract them from losing all their files...
now please don't tell me that it can never happen, because we all know it can, and most people aren't against the locking itself, but that there is no forced method to unlock.
for those of you that haven't read the draft, it specifies a requirement of having a standard way to unlock the mouse.
the link to that draft is up there under title of this article. it says "source: Google", go ahead click it and read.
i understand very little of what is worte about in that doc, if its true, than great, a bit of my above statement can be retracted.
is there any way to exit out completely, and in stop the c++ from running at all?