I appreciate the gesture, but hasn't the ship sailed? It seems hard to imagine that we'd e.g. undo the coupling of encapsulated styles to SD in favour of a declarative mechanism, or eliminate attributeChangedCallback in favour of a unified interface for passing data to components
-
-
I think you're missing the point here — there is real confusion caused by the dual interface of attributes and properties. The C++ implementation is utterly irrelevant to me as a component author and consumer
-
I grok the point. That DOM has both is clearly not great! MSFT's DOM was correct (and Netscape/IBM were *super* wrong). But if you want property-only components, or want to only handle attributes up-front, can do that today. What's missing?
- 11 more replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.