Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

@matthewp @Zambonifofex

I believe attributes should be on a per-custom-element basis, otherwise globally registered attributes will get *messy quickly*. Many custom elements may depend on values of attributes with the same name (I.e. name clashing can become a nasty problem).

In native HTML, `style=""` is common across many elements, if not all. This type of thing should happen through extension. If my custom element has special behavior based on a `foo=""` attribute, and you extend it to make your own custom element, then your element will inherit that attribute behavior. Likewise, we can explain the `style` attribute the same way due to the fact that custom elements can inherit it from HTMLElement (I think that is where style behavior is defined?).

-- 
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/509#issuecomment-246120909