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

> imho, when authoring html, it feels more natural to say: "i want a my-fancy-select custom element, but just in case something isnt supported (client fault) or configured wrong (server fault) or failed to download (infrastructure fault), then treat this thing as a normal select.

So how would your case work if loading in an older browser, or text-browser like `elinks` that does not have JS at all?  They are just going to see `my-fancy-select` and ignore it, they do not know what the `fallback` attribute is, thus this example completely and entirely fails for a progressive web page.

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