Re: [whatwg/dom] Declarative Shadow DOM (#831)

> > > I'm pretty sure I've said this in the past but we consider the integration of _closed_ shadow roots with custom elements as a **must have**. We can't support this proposal unless that is spec'ed out. Otherwise, this feature provides zero benefit for developers who are using closed shadow trees.
> > 
> > 
> > @rniwa I believe we have defined a path forward for closed shadow roots support, mostly explained here: https://github.com/mfreed7/declarative-shadow-dom/blob/master/README.md#existing-declarative-shadow-roots. Do you think we need to have that part spec'd as well or can we just keep it as a separate feature associated to element internals?
> 
> Yes, that part definitely needs to be spec'ed out. Recall that our position has been that people should be always using closed shadow roots, not open shadow roots. Without this part being figured out, all basis and arguments to have declarative shadow roots is basically moot.

Thanks for the comments, @rniwa. In the interest of trying to move this feature forward, I'd like to get a few clarifications:

- While we disagree about the benefits and issues associated with streaming support here, I think we've reached somewhat of a consensus that streaming support can be added later, with something like `<template shadowroot=open streaming>`. So let's table that part of the discussion.

- As @caridy points out, we've discussed closed shadow root support in the [explainer](https://github.com/mfreed7/declarative-shadow-dom/blob/master/README.md#existing-declarative-shadow-roots) and in [Issue 871](https://github.com/w3c/webcomponents/issues/871). You are saying that without resolving [Issue 871](https://github.com/w3c/webcomponents/issues/871), you cannot support this declarative Shadow DOM proposal. I understand your concern, and I'd like to solve it. But is the inverse of your statement true? I.e. if we resolve [Issue 871](https://github.com/w3c/webcomponents/issues/871), could you then support declarative Shadow DOM?

I've just [proposed a fix for Issue 871](https://github.com/w3c/webcomponents/issues/871#issuecomment-672082936), which I will commit to implementing in Chromium immediately, if agreed upon. Please take a look there, and let's get that issue resolved. And then I'm hoping you'll be supportive of this proposal.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/831#issuecomment-672083801