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

I'm more concerned when subclassing more specific elements becomes common place. Currently implementations are not widespread. Specific elements are more likely to need new attributes.

Normally, when new top level APIs are added, they are shadowed by the page's global variables. When properties are added to prototypes, they're shadowed by subclasses. That's not the case for attributes.

This is also a new scale of the problem. Currently there is some non-conformance as can be expected but not to the extent that custom-elements are going to be used. I had a hard time finding a single component on https://www.webcomponents.org/ that *didn't* use a non-hyphenated name. At the very least, there's a messaging problem here.

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