MouseLock feedback

Hi all!

Vincent was kind enough to share his most excellent spec
(http://dvcs.w3.org/hg/webevents/raw-file/default/mouse-lock.html). I
have a few questions/suggestions:

1) The case of cross-origin frame isn't handled properly with
document.mouseLocked. We probably shouldn't return an element from a
cross-origin frame, but returning nothing seems bad, too. Perhaps we
should separate the queries of "is there a mouse lock in effect?" and
"which node has the lock"?.

2) "mouse" seems too narrow. There's already a perfectly nice
"pointer" term, which is used in pointer-events, and it appears much
more inclusive of the newfangled touch pads and touch screens.

3) Putting the API on the document is misleading. There's only one
pointer on the device, and you aren't really locking things per
document. Also, the document is already a huge pile of methods and
properties. Perhaps instead we should use Navigator as the right
place? Something like this:

navigator.pointer.lock(element, failureCallback, successCallback);
navigator.pointer.unlock();
navigator.pointer.isLocked();

WDYT?

:DG<

Received on Wednesday, 26 October 2011 18:41:19 UTC