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

> Why do you think that is the case? We've loosened the validation rules, but I don't believe we've encouraged using such attribute names.

My language could have been better. People haven't been discouraged from using non-prefixed names, and I'm not pointing fingers at the working group or any group in particular. Every example I've ever seen (and that's quite a bit) has always used un-prefixed names (unless using dashes to separate words).

Validation rules aren't the issue here. The issue is if a conflicting name is added to the spec. It could unknowingly break an incalculable number of custom elements in the wild.

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