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

> What's the reason for needing to err on the side of caution here?

One reason is that the implementation cost.  Implementing a shadow piercing combinator requires a significant implementation effort, which can be directed instead towards other efforts like [adding light style mechanism to custom elements](https://github.com/w3c/webcomponents/issues/468) and/or one of thousands of other features being proposed.

> 100% of @rniwa's comments are based on a conflation of open and closed shadows.

Have you even read my comments?  Nothing but the first paragraph in [my earlier comment](https://github.com/w3c/webcomponents/issues/78#issuecomment-238672734) is related to shadow tree modes:
> For example, propagating Rect-render-like states to subcomponents is NOT an appropriate use case for `/deep/` since it won't be one off case to bypass encapsulation.  This use case is better met by a new custom element callback designed to propagate states top-down.
>
> Writing [integration tests](https://en.wikipedia.org/wiki/Integration_testing) for a Web app consisting of hundreds of components is another use case that came up.  I'd argue that such an integration test should not be relying on internal states of each component.  Instead, they should be testing based on each component's public interface.  However, if authors really wanted to do white-box testing across components, they could simply write an equivalent of `/deep/` in JavaScript.  And this would be fine for testing scenarios because an extra runtime during testing wouldn't hurt end users.

> I think the only thing that will happen by excluding this is that the usability of open shadows and adoption of Web Components will be hampered.

Why would the lack of shadow piercing combinator hamper the usefulness of shadow trees if it were only used during testing and other kinds of extraordinary situations in which one has to bypass the encapsulation provided by shadow trees?  What exactly are use cases in which this feature is required?

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