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

> Does that mean every specifications proposal that proposes adding a global attribute will be constrained by this?

I think this is already the case as [Anne mentioned](https://github.com/w3c/webcomponents/issues/654#issuecomment-320883733):

> 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.

For example a popular jQuery plugin or framework could add its own attributes.

-- 
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-339397301