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

I just wanted to add a (possibly separate) thread to this conversation.  I may turn this thought into a separate proposal after mulling it over (unless I hear that it is obviously something we would do even if I didn't propose it).  Whether or not the platform decides to officially support  "binding from a distance" *in addition to* inline binding, which is my preference, I think, as someone who is finding scenarios where binding from a distance is quite useful, that this is the most important thing -- it ties in, actually,  with something I've tried to articulate, possibly with only partial success, in my [custom enhancements](https://github.com/WICG/webcomponents/issues/1000) proposal:

Hopefully, someday soon, we will start seeing concrete implementations built into the platform, via inline binding, for things like for-each.  It would be great if in addition to supporting such functionality that gets triggered by the presence of inline binding via handlebar syntax, we could **also** programmatically attach (connect?) that functionality programmatically, i.e. something like:

```JavaScript
oElement.bindings.attachForEach(List, repeatingTemplate, repeatingTemplateParts);
```

The truth is, I think, implementing a "binding from a distance" solution is fairly easy in userland, (well, some of the syntax @matthewp  is showcasing, which looks really cool, might not be so easy).  It's the actual heavy investment in the  grunt work behind the nested looping, conditionals, etc. that (I) would want to be able to leverage "from a distance". 



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

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