Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180)

Thanks for the comments!

So roughly,
* `document.fullscreenElement` can point to a shadow host, and its `shadowRoot.fullscreenElement` points to the fullscreen element (or a shadow host, recursively)
* `:fullscreen` matches to those shadow hosts (can be multiple, if shadows are nested multiple times)
* `fullscreenchanged` / `fullscreenerror` events are dispatched to `document`
* If a slotted element becomes fullscreen, the slot's `shadowRoot.fullscreenElement` is `null` (like concluded in #358 for `activeElement`).

Probably we can consider firing those events to `ShadowRoot` before they are fired to `document` in v2.
As `document` should be accessible to those shadow trees, we don't need `ShadowRoot.exitFullscreen()`.


---
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/180#issuecomment-224244250