Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78)

Look at any non-WC page that searches for elements in the page with querySelector/All(), for any reason.

Now, imagine they switched to make heavy use of WC, such that there was a nice hierarchy of shadow trees.

Boom, that's a use-case.  (Unless you can reasonably argue that, in the new version of the page, they'll have *no need* to search for elements from the top level of the page anymore, and can rely on specific elements to do all the searching locally within their own tree. That would be a difficult argument to make, I think.)

And as a reminder, *not* having `>>>` in qSA() has nothing to do with safety or encapsulation.  You can emulate its effects perfectly, if with some effort and cost, by manually parsing the selector, then tree-walking the open shadow trees and running selectors yourself.  It only exposes information that is already freely exposed via DOM APIs.

-- 
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/78#issuecomment-334900442