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

Yes, webkitfullscreenchange fires on an element and bubbles, except in some funny cases where there is no element. I think this could be spec'd in some mostly reasonable way, but as you say the web is good at surprising browser developers.

Until we decide to try to spec the prefixed Fullscreen APIs I suppose we'd all leave our prefixed APIs alone as much as possible, just trying to think through the fallout.

Assuming that we *did* make that change to Fullscreen, would it solve the problem in this issue?

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