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

In real life, shadow DOM encapsulation is used for many different purposes. One is css isolation for example. That does not mean that all applicative features should respect all these encapsulations.

In my app, I use intensively ShadowDom. I have 2 libraries for scanning nodes. "DOM" without crossing ShadowRoot, and "DOMSH" for Shadow abstraction. I have counted the uses of these libraries in my project core code : ~1300 calls for DOM and ~650 calls for DOMSH.

My 2 cent's: Selection is a transversal feature, we sometimes want to use intra-shadow approach, sometimes the inter-shadow approach. You should offer both.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/79#issuecomment-943110580