Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035)

> As an aside, I don't know how I come across when I'm writing on a thread like this. I hope you also know that I'm not trying to be antagonistic. I genuinely want to understand the concerns and I'm really interested in seeing viable alternatives. We definitely need more diversity of thought in this area.

Thank you for stating this! I hope you that you see that I am also not trying to be antagonistic. I would only caution against statements like this:

> Let's keep iterating. We need a concrete workable alterative if there is really dissatisfaction with the current direction. Any new proposal has to address the core set of requirements as well as the concerns that browser vendors have raised with past iterations of dom parts.

This comes across, I'm sure unintentionally, as telling people what types of feedback is and is not valid. That should not be the case. If people (myself for example), think that the requirements *themselves* are wrong, or that there are *missing* requirements, those are things we should able to talk about. In summary, don't try and box in the conversation.

I'm sure that you're trying to help by providing context for what you think browsers will accept. I would rather state my viewpoints, plainly for all to see, and be ignored, than be talked into giving a narrow feedback that only allows tweaks. My viewpoint is that templating as a solution is *inherently* against the core principle of the web of being server-agnostic, and that is where my feedback and counter proposal comes from.

Appreciate your willingness to discuss this and thank you for this note! 💚

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1035#issuecomment-1805771249
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1035/1805771249@github.com>