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

> Now let's say this element is in production, correctly responding to the semantics of its custom hidden attribute. Then along comes a new, standardised, attribute with of the same name in what normally would be an innocuous change. The new attribute takes the element and hides it immediately. All of our custom elements that implement our own semantics for this attribute are now broken.

Basically, this is exactly why using the same rules for attribute names as for tag names (as per custom naming) is the worst idea ever, and also why one should not just invent attribute names they deem appropriate.


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