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

Adding global attributes to the platform is pretty rare, but it must now be done with the understanding that custom elements exist and should not be broken or overly burdened. Namespacing attributes was not part of the core design of custom elements (as, for example, was naming them with a dash) and therefore is not required or encouraged.

There are a variety of ways to add global functionality like attributes that does not conflict with existing custom elements: (1) it can be added above HTMLElement or a cutout for custom elements can be made, (2) it can be customized/overridden via custom elements features (e.g. attributeChangedCallback, observedAttributes, etc.), and of course (3) additional features (v2 spec) can/should be added to custom elements to allow deeper integration with the platform as it evolves.

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