Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)

Thanks for the implicit feedback on my proposal.  There are some nice ideas here I may steal if that's okay, with "attributions"  (sorry for the bad pun) (and apologies for overlooking your original 2017 proposal, will add a link to that for sure).  I remain unconvinced of this direction (but I will see if my reasons hold merit on reflection).  It seems I am in a minority of one, but I will continue slogging along at my proposal, incorporating ideas such as these, in case we find a happy compromise.

For starters, it seems that the feedback is that my proposal is too complicated, so I will look for a better "on ramping" experience.


One concern:

```
// This also works:
MyInput.attributeRegistry.define("ac-list", ListAttribute, {
 propertyName: "autocompleteList" // if we want to override the default acList
});
```

This means that in order to register the attribute, then we need to wait for the MyInput class to be downloaded.  But if we use whatever we call this thing-of-a thingy for doing cross cutting things (like binding during template instantiation, for example), I think that could be an issue.

I'm curious if you could provide insights on this question:  When I look at this (documentation)(https://mavo.io/docs/plugins), it seems that by default the "hooks" can apply to all elements by default.  Likewise when I look at [Vue](https://vuejs.org/guide/reusability/custom-directives.html#directive-hooks) and others (knockout.js) etc.  My proposal was heavily influenced by what I see in industry (as that seems like a proven model?)

It seems that by default we are deeply curtailing the developer's "reach" and I'm puzzled as to why?  Is it parsing constraints?

I agree we want the developer to be able to curtail their own reach, but I'm a bit surprised that that is the direction this is taking?


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

Message ID: <WICG/webcomponents/issues/1029/1718285623@github.com>