for example) be specified to automatically fail?
Regards,
Chris Pearce.
On 1/10/2014 4:08 AM, Ms2ger wrote:
Hi Vincent,
I have by no means reviewed the entire spec, but while reviewing the
test cases, I noticed some room for improvement. Comments below.
In the 4. pointerlockchange
lock fine in Firefox and Chrome release
builds.
https://github.com/toji/game-shim
Chris Pearce.
likely to be read.
Chris Pearce
won't pay attention to an approval
prompt shown after entering fullscreen, then the same argument also
applies to showing the approval UI before entering fullscreen.
Regards,
Chris Pearce.
browser may not be appropriate for a tablet, for example.
Regards,
Chris Pearce.
[1] I believe it is
Last Call Ready.
I agree. No one involved on our side of things is aware of any remaining
issues with the pointer lock spec.
Chris Pearce
(Mozilla's pointer lock implementation maintainer)
that we want this behaviour, and get the spec changed to
reflect that.
Regards,
Chris Pearce.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=779286#c18
On 2/06/2012 11:19 a.m., Vincent Scheib wrote:
IMHO Pointer Lock would be more convenient to use if events are sent
to the target element as well, and not just the document.
Is there a reason the Fullscreen specification doesn't dispatch events
to the most relevant element?
Because we exit
On 19/05/2012 4:25 a.m., Anne van Kesteren wrote:
Chris Pearce is not on this mailing list. Chris are you okay with
moving discussion to here? Anyone else who should be kept in the loop?
I'm happy to move the discussion to public-webapps, thanks for the heads up.
Cheers,
Chris P.
