Re: [webcomponents] Shadow DOM and requestPointerLock() (#192)

I don't know yet.

I'm not currently sufficiently familiar with Shadow DOM, and in 15 minutes could not understand open/closed trees, and thus do not understand the discussion in #180 for Fullscreen. I also don't fully understand andyearnshaw's fullscreen usecase. 

>From my simplistic understanding, Pointer Lock should work for any node in a tree that can eventually (even through shadow DOM boundaries) reach the root document node of a frame. 

Permission should be controlled by a single origin.

Lock should be exited if the node is no longer in the tree (as above), or navigation, or loss of document focus.

Generally, if a shadow node has lock and there's a need to disambiguate that element, the `shadowRoot.fullscreenElement` concept seems to be reasonable, but I don't really understand it yet.

I can contribute more to this discussion after either finding more time to learn Shadow DOM or by answering more specific questions Shadow DOM folk have.

---
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/192#issuecomment-197601928