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

This is actually a problem even without https://github.com/whatwg/fullscreen/issues/74, since the `fullscreenchange` event per spec is fired at animation frame timing.

WebKit has code to fire a second event if the element is removed, and in my last attempt to match the spec in Blink I ended up changing `webkitfullscreenchange` to check if the element is still [connected](https://dom.spec.whatwg.org/#connected) to the correct document, and if not using the correct document as the event target instead. I took some inspiration from https://w3c.github.io/webappsec-csp/#report-violation where the event target depends on the circumstances.

I think we could make it work if we wanted to. So far it's seem like a hassle, but if we could fix a problem like this and alias the prefixed event, it looks more worthwhile.

-- 
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-279898962