On Tue, Jan 13, 2015 at 4:56 PM, Mike de Boer <mdeb...@mozilla.com> wrote:
> 1. Optional access to the hardware pointer/ cursor as a possible extension to
> the pointerLock(Element) API to have better performance when capturing the
> cursor and the optional ability to restrict mouse movement within a rect. One
> example might be:
>
> requestPointerLock({clipRect: [0, 0, window.innerWidth, window.innerHeight],
> useHardwareCursor: true})
>
> … where clipRect could also be a DOMRect (if it can be instantiated from
> content), for example. The point here is to allow for more control over the
> cursor and accessibility to a more direct pointer layer.
They could do this by just having a dummy element, no? Is this being
suggested because of the other suggestion in which case you wouldn't
want to have such a dummy element overlaying a part of the screen?
> Is WebGL game development something we ought to focus on and cater to?
Making the web attractive for gaming seems extremely relevant to what
we are trying to do overall, so yes.
--
https://annevankesteren.nl/
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
