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

> > how do **developers** benefit

> I don't think that's the relevant question. We have a design goal of parity and this doesn't meet that design goal. That's the high-level bit for me.

To me, developers, and their end users, are the reason we're working on this platform. The point of having a design goal for **anything** should be that it benefits developers and/or users. If it instead limits developers, and we do it just to make  the spec more pure, then I think [this link is relevant](https://www.w3.org/TR/2007/WD-html-design-principles-20071126/#priority-of-constituencies). It sounds like perhaps the "parity" design goal needs to be re-evaluated?

The `open` and `closed` parity is an odd dimension to try to maintain: these are *designed* to be different, specifically along the dimension of access control to the shadow contents. However, I think there **is** a parity that is important to try to maintain: imperative vs. declarative versions of the same API. Those should provide equivalent functionality. Any difference is a) confusing, and b) limiting.

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

Message ID: <whatwg/dom/issues/831/1693970286@github.com>