[whatwg/fullscreen] `fullscreenchange` should behave like `webkitfullscreenchange` (#89)

At the moment, my understanding is that `fullscreenchange` fires on the document while `webkitfullscreenchange` fires on the element that enters/exits fullscreen and bubbles up to the document.

I see the following reasons to keep the `webkitfullscreenchange` behaviour:
- compatibility: likely, some websites that try to assume a non-prefix API will exist add the event listener to the element and simply change the event name. I definitively tried to do that once until @foolip told me I'm wrong;
- simplicity/less error prone: it will increase the chances of developers to trigger behaviour change when a specific element goes fullscreen instead of anything inside the document (ie. it is easy to not check which element is fullscreen when the document becomes fullscreen).

The only reason I see to fire the event on the document is for the API to be wrapped around the `Document` interface instead of being spread around multiple interfaces but it's already the case with `enterFullscreen()` so maybe that battle is already lost?

-- 
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/issues/89