Hi Vincent, All - given there were no negative comments regarding
Vincent's proposal, Doug and I will work toward updating WebEvents'
charter to add the Mouse Lock API.
Additionally, as indicated in [1], we will also work toward adding the
Gamepad API [2] (formerly know as the Joystick API) to WebEvents' charter.
-Art Barstow
[1] http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1408.html
[2] http://dvcs.w3.org/hg/webevents/raw-file/default/gamepad.html
On 9/15/11 1:52 PM, ext Vincent Scheib wrote:
A Mouse Lock API has been under discussion on the W3 public-webapps
list "Mouse Lock"[1] and earlier "Mouse Capture for Canvas"[2].
The primary goal is to enable use cases such as first person
perspective 3D applications. This is done by providing scripted access
to mouse movement data while locking the target of mouse events to a
single element and removing the cursor from view.
I have been working to formalize the discussions into a draft
specification[3]. I propose that the Web Events Working Group consider
adoption of Mouse Lock for formal specification.
Cheers, -Vince
1.
http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/thread.html#msg960
2.
http://lists.w3.org/Archives/Public/public-webapps/2011JanMar/thread.html#msg437
3. http://goo.gl/9G8pd
Additional discussions:
W3 issue: http://www.w3.org/Bugs/Public/show_bug.cgi?id=9557
Firefox issue: https://bugzilla.mozilla.org/show_bug.cgi?id=633602
Chrome issue: http://code.google.com/p/chromium/issues/detail?id=72754
