W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: Fullscreen events dispatched to elements

From: Chris Pearce <cpearce@mozilla.com>
Date: Sat, 02 Jun 2012 13:45:24 +1200
Message-ID: <4FC97034.3000200@mozilla.com>
To: Vincent Scheib <scheib@google.com>
CC: Webapps WG <public-webapps@w3.org>, Anne van Kesteren <annevk@opera.com>, Jer Noble <jer.noble@apple.com>, whatwg <whatwg@lists.whatwg.org>, Robert O'Callahan <robert@ocallahan.org>
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 fullscreen when the fullscreen element is removed from 
the document, so if you dispatch events to the context element, the 
"fullscreenchange" event never bubbles up to the containing document in 
the exit-on-remove case.

Because of this, the spec was then changed to dispatch fullscreenchange 
to the context element on entering fullscreen, and to the document on 
exit, but we found this inconsistent, since a listener has to listen to 
multiple nodes to receive both exit and enter events, so the spec was 
changed again to always dispatch "fullscreenchange" to the document.


Regards,
Chris P.
Received on Saturday, 2 June 2012 01:46:02 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT