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

@EduardoRFS `is=` is not perfect, but without something in the markup that defines what a custom element's superclass is, progressive enhancement and a lot of a11y are broken. In [my first comment](#issuecomment-256499447) I pointed out five things that `is=` solves that can't be solved with JavaScript.

The other example @tomalec provided of a subclass of `<template>` would also not work with a solution that depends on JavaScript because a browser that has JavaScript disabled would render the element's contents which a `template` is not supposed to do. The browser needs to know that `<our-template></our-template>` is an instance of `HTMLTemplateElement` *before* JavaScript runs.

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