Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79)

Basically, the idea is to provide a mechanism to refer to a specific position within a shadow DOM with a mechanism that can be also used to refer to a specific position in pseudo element, SVG use element's shadow tree, etc...

It's probably sensible to introduce an interface on `ShadowRoot` to see the boundary points within a specific shadow tree but that shouldn't be [`Selection` interface](https://w3c.github.io/selection-api/#selection-interface) since that interface has a bunch of methods like `collapse` and `extend` which don't make sense to have it for every shadow root.

We also discussed that we need a mechanism to pick a mode between having a separate selection & having a selection that's shared with the parent tree. e.g. if you're creating an editor, you may want to have its own selection whereas if you're just an article, you probably want the selection to be shared with the rest of the document.

-- 
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/79#issuecomment-344161666