Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614)

I don't quite have idea why Gecko would take compat risk by trying to switch the behavior to something similar to what WebKit and Blink currently do for webkitfullscreenchange. And I don't understand why (1) doesn't work for fullscreenerror either.

The fullscreenchange event for entering fullscreen is probably not too hard. The tricky thing is that for exiting fullscreen... yeah, if the element is removed from the document, we need to find something to dispatch the event on... and also if we change the document state synchronously but dispatch event asynchronously (as proposed in whatwg/fullscreen#74), the document tree may be mutated just before the event dispatch as well.

I don't have strong opinion here. I guess I'm fine with either... (Perhaps I miss some difficulty... I don't know...)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/614#issuecomment-279698457