Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)

If we either:

1.  Move the binding out of the template, like what is done with [trans-render](https://github.com/bahrus/trans-render or possibly the [corset](https://github.com/matthewp/corset) libraries, that's one way to avoid needing to pass the template instance (for simple to rather complex scenarios) down.  (I am struggling with the proper syntax to account for certain interpolating scenarios, between a closing tag and opening tag).
2. For inline binding, I think it would possible, at least for simple to moderately complex streaming declarative ShadowDOM, to reverse engineer the output to infer what the template should look like with inline binding, especially if that (future?) requirement is considered when formulating what the processing instructions should look like.

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

Message ID: <WICG/webcomponents/issues/1009/1527933690@github.com>