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

What do "non-JS backends" or what I would probably term "server-only backends," do for interactivity?

If you don't send any JavaScript to the client, and have no support for client interactivity, then you have no client JavaScript to replace, and DOM parts in its initial form won't help you. If DOM parts were purely declarative, it could help you, with extensions of other APIs like `invoketarget` etc. And we're interesting in that in future iterations of this proposal, but it's too much to take on from the outset.

In some of your posts you've made it seem like there is a zero-sum situation, and I'm not sure I share that mindset. This API in my mind has a clear target of what code it wants to replace and what use case it wants to solve. That doesn't mean that there aren't other APIs solving other categories of problems, and I'd welcome a clearly stated user need and solution for your own requirements.

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

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