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

Hi @trusktr , I need to read through your ideas, but having just skimmed it, I'm kind of excited to see we might be converging in views -- I've added support for observableAttributes to [my proposal](https://github.com/WICG/webcomponents/issues/1000), based on the "lightning bolt" that emanating from @sorvell 's comments.

However, I was just sitting down to correct my approach -- I *think* we want the list of observable attributes to provided in the registration function, rather than a static property.  I think the registration is the key place that should control the property name off of the enhancements property as well as the attributes, so we can concentrate all our scoped registry trickery in one spot.  I also agree with you I was probably overthinking the namespacing a bit, I think we can probably trust developers to make such judgments for themselves (as long as we insist that attributes have dashes, and I still think we need a prefix when applying to third party custom elements.

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

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