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

OK - Let me reboot my simple scenario and limit it to custom elements and javascript in general.  

SIDE NOTE my background and primary reason for looking at all the specs is that I think custom elements and the shadow dom are fantastic tools for simplifying my apps, and my gut feeling is that anytime I create an element that does something beyond just special effects, the app will break given that the custom element API is not supported.  I'll illustrate what I mean.

So suppose I wrote an app consisting of two custom elements `<custom-broadcast>` and `<custom-receiver>` that talk to each other.  The `<custom-broadcast>` elements sends messages on a configurable attribute channel and `<custom-receiver> ` receives them on a configurable attribute channel.

I could also have a `FancyButton` configured as `<button is="fancy-button">Broadcast</button>`.  When I click the button it will tell the `<custom-broadcast message="Cubs win!!!" channel="1"`> element to start broadcasting **Cubs win!!**  and the `<custom-receiver channel="1">` will just log that to the console.  

So I load this app in a browser that does not support custom elements.  The FancyButton falls back to a normal not so fancy button, and when clicked nothing works.

So to me it seems as if I want an app that works well on all browsers, then I'm better off with a non custom element approach, but if I want to go bleeding edge and throw some users with dusty browsers under the bus then I would choose custom elements.  

In other words I simply don't see what advantage `is` is offering?

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