Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90)

If we want to do this, we should pull back hierarchy restriction first.

Before we do this, I'd like to ask if anyone recalls why it is currently fired on the document?

It seems to me the [initial proposal](https://wiki.mozilla.org/Gecko:FullScreenAPI#fullscreenchange_event) from roc was to dispatch it to the element, and I don't find any mention of why Gecko doesn't follow that way in [the bug of the initial impl of this API](https://bugzilla.mozilla.org/show_bug.cgi?id=545812). Probably the current spec largely follows how Gecko is implemented, and it was just a history mistake to fire on document?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/pull/90#issuecomment-303081371