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

The essence of this proposal is standardizing on a way to mark a location in the DOM and associate values and metadata with it. There is a fully declarative way of doing this, and there is an accompanying imperative JS API as well. 

This feature should be usable with any server framework by simply generating HTML with `{{}}` markers. Server frameworks can provide values that render immediately without the need for JS and can also associate arbitrary metadata at those locations as well....which could be used by JS to power a front-end renderer, or it could be used for entirely different purposes, such as to power a Turbo-like or HTMX-like system.

The proposal does not provide a declarative way to update the DOM, only an imperative way AT THIS TIME. There is a desire to provide a declarative way to enable updates as well, but that was thought to be too much in the first version as it would pull in a lot of other features/work that hasn't been figured out yet and requires a lot more community discussion. Instead, the idea was to create an open syntax that could be expanded in the future to enable built-in and custom declarative syntaxes.

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

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