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

@WebReflection Those are some great examples (^_^)

@oleersoy To add to the previous comment, `<app-drawer>` wouldn't necessarily break in browsers that don't support custom elements if it's implemented in the right way. You should check out [this video of how to make a progressively enhanced accordion custom element](https://www.youtube.com/watch?v=P2glQ0fz7DM) by the Chrome Dev team (more links below). Try looking at it (in Chrome) with and without JavaScript. It's just a demo so it doesn't go as far as checking for custom element support in browsers other than Chrome, but you can get the idea.

The reason an `<app-drawer>` doesn't need `is="something"` is because it doesn't need to fall back to a particular element type. When `is=` is not used, a custom element will just fall back to a plain `HTMLElement` and it will work, because all of the browsers will display an element with any tag name. Luckily, that's been in the spec since long before custom elements have been a thing and will work regardless of the fate of `is=`.

[Chrome Developers Supercharged - Accordion](https://www.youtube.com/watch?v=P2glQ0fz7DM)
[Source code from the video](https://github.com/GoogleChrome/ui-element-samples/tree/gh-pages/accordion)
[The final product](https://googlechrome.github.io/ui-element-samples/accordion/)

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