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

Re: [whatwg] Fullscreen events dispatched to elements

From: Jer Noble <jer.noble@apple.com>
Date: Mon, 04 Jun 2012 22:57:02 -0700
Cc: Chris Pearce <cpearce@mozilla.com>, Vincent Scheib <scheib@google.com>, whatwg <whatwg@lists.whatwg.org>, Webapps WG <public-webapps@w3.org>, Anne van Kesteren <annevk@opera.com>
Message-id: <5AA8DF56-6A2A-4376-B434-CC49B81E7A5F@apple.com>
To: robert@ocallahan.org

On Jun 4, 2012, at 10:43 PM, Robert O'Callahan <robert@ocallahan.org> wrote:

> On Tue, Jun 5, 2012 at 9:13 AM, Jer Noble <jer.noble@apple.com> wrote:
> On Jun 1, 2012, at 6:45 PM, Chris Pearce <cpearce@mozilla.com> wrote:
> 
> > 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.
> 
> Actually, in WebKit, we explicitly also message the document from which the element was removed in that case.  I don't see why this behavior couldn't be standardized.
> 
> Did you inform the spec editor(s) when you decided to make this change? What did they say?

As it is a holdover from when we implemented the Mozilla Full Screen API proposal[1], which required that behavior, no.

-Jer

[1] https://wiki.mozilla.org/Gecko:FullScreenAPI#fullscreenchange_event
Received on Tuesday, 5 June 2012 05:58:09 GMT

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