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

`shadowRoot.fullscreenElement` makes sense to me too. Would there be any difference between open and closed shadow trees?

FWIW, fullscreen *inside* a shadow tree doesn't currently work correctly in Chrome, because it still has the `:-webkit-full-screen-ancestor` selector that's needed to make the ancestor "get out of the way", so to say. And there's a that the ancestor traversal stops at the shadow boundary, so not all (composed) ancestors match this selector. That'll be fixed by https://bugs.chromium.org/p/chromium/issues/detail?id=370459 hopefully.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/180#issuecomment-194669901