Pointer lock spec[1] has been updated as I described, with the exception of allowpointerlock which still needs to be added. http://dvcs.w3.org/hg/pointerlock/raw-file/default/index.html
Feedback welcome. On Fri, Jan 27, 2012 at 9:06 PM, Vincent Scheib <sch...@google.com> wrote: > The spec for Pointer Lock has been moved[1]. It was also renamed from the > previous "Mouse Lock". > > While landing the initial implementation in WebKit Darin Fisher pointed > out that the Fullscreen API[2] had strong overlap with the pointer lock > spec in dealing with entering and exiting a state targeting a particular > element. To simplify the web platform, and because these features will > often be used together, I'm planning on revamping the pointer lock > specification to match the Fullscreen spec as closely as possible. > > Specifically, using: > > partial interface Element { > void requestPointerLock(); > }; > > partial interface Document { > readonly attribute boolean pointerLockEnabled; > readonly attribute Element pointerLockElement; > > void exitPointerLock(); > }; > > Events: pointerlockerror, pointerlockchange > > iframe attribute: allowpointerlock > > The previous MouseEvent addition of movement is unchanged: > > partial interface MouseEvent { > readonly attribute long movementX; > readonly attribute long movementY; > }; > > Stakeholders of the Mozilla/Firefox implementation have indicated support > for this transition. > > Comments / Feedback welcome! > > [1] http://dvcs.w3.org/hg/pointerlock/raw-file/default/index.html > [2] http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html >