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

Hi @LeaVerou ,

I for one vote overwhelmingly to support svg (I was proposing that by extending "ElementEnhancement"), and I think it is up there in the top complaints / limitations for custom elements.  So unless there's a solid reason not to, why wouldn't we?

(mis)reading your proposal further (apologies in advance):

>Associating enhancements with a selector would probably afford maximum flexibility and allows the association to happen implicitly.

I'm getting a little lost here.  Is your proposal heading in the direction of allowing each custom attribute to "opt-in" to be a behavior?  Is that why you are considering the "has" attribute?  Is basing access to the name of the behavior based either literally on the custom attribute, or the camelCase string problematic?

Either way, I'm not following some of the discussion (apologies, again), but have you yet settled on how third party vendors can access the behavior, what that looks like (and how to make that seamless), or is that a work in progress?  Are attributes required to enhance an element?  If so, why?

Feel free not to answer, just wanted to convey what I'm looking for to be 100% satisfied, and what I'm finding difficult to follow.  





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

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