Re: [WICG/webcomponents] [idea] Make use of `observedAttributes` optional (#565)

Note that @hmans case isn't that unusual. A-Frame hit the same issue with their Entity-Component-System, and it kept them on the v0 specs for a long time. I think they might solve this by patching `setAttribute` and reading all attributes at connected, which obviously has some problems. Maybe they use a MutationObserver too.

I remember in the very early group meetings that Elliott Sprehn proposed some kind of wildcard with a sigil that would exclude `style` and `class`. My recollection is that the idea wasn't shot down, just deferred until later if a need came up.

btw, @hmans a solution that works with `observedAttributes` would require some kind of runtime or build-time introspection on the type of object being wrapped. If class fields were present on the prototype in some way, you'd be able to do something, but instead maybe you can introspect the source.

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