Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78)

Unfortunately, we haven't had a time to fully adopt `collectMatchingElementsInFlatTree` in Safari code yet but we've just started working on this again this week. We'll let you know.

We think we need some mechanism to walk over the flat tree in browser extension code and scripts injected by web driver tests since many of these scripts already have to walk across cross-origin iframes to be useful in some cases, and they are sort of *privileged* scripts that can ignore other security constraints.

We're still extremely cautious and skeptical that such an API is needed for production website code since most of use cases we're aware of involves violating the very encapsulation layer shadow DOM aims to provide. While author can always bypass such a boundary in JS (e.g. each component can eagerly expose its `ShadowRoot` as a JS property even for a closed-mode shadow tree), we're very much afraid that lowering the barrier of such a violation by providing an selector-based API would undermine the very purpose of shadow DOM.

-- 
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-275059032