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

@matthewrobb Indeed, nesting elements like that to fallback to native elements was what we suggested as one alternative to many use cases raised by people advocating for `is`. In fact, this is precisely how fallback works on the Web.

Let it be `canvas`, `iframe`, etc... when those elements aren't supported, the browser shows the content inside of it. e.g. you might place `img` inside `canvas` to fallback to non-interactive element in a browser that doesn't support canvas. For progressive enhancement purposes, this works perfectly fine.

What it comes short of is when you want to leverage the capability of builtin elements. For example, it's not easy to replicate all the functionalities various input element types provide. For those use cases, we've argued that we need to:
 1. Provide a proper API to participate in a form submission
 2. Provide a mechanism to customize the appearance of form controls.  Like -webkit-appearance but more powerful and standardized.

Why? Because in vast majority of use cases we studied, what Web developers want is the ability to override or customize the appearance or the user-interaction model of builtin input element types. Since `input` doesn't support shadow DOM at all, this isn't even possible even if we had the support for `is` attribute.

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