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

Since (custom) attributes are not supposed to include upper alphas, a possible solution would be to require that future global attributes do contain at least an upper alpha. For example, a future "undoscope" global attribute would be "undoScope" (or "UndoScope"?). That seems easier to police than retroactively imposing a restriction on the naming of custom attributes of custom elements.

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