Re: [w3c/webcomponents] Custom attribute names conflicting with built-in attribute names (#654)

> I suspect the rationale was that we always have to do some research which attribute names are still available when minting a new global attribute name as we're not allowed to break non-conforming content (at least not when it's widespread) either. Backwards compatibility is not limited to the good stuff.

That makes sense now. I wonder if there is some way to allow attributes to behave more like properties or methods as opposed to going down the road of namespacing and discouragement.

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