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

> `<noscript>` works just fine in elinks, even with table, tr, td.

so you are in favor of duplicated layouts all over the modern web, correct?


> We don't need to make new technology based on very outdated technology.

The point is progressive enhancement, not outdated technology.
You'll still put the input inside your shadow DOM.
Using an input has nothing to do with promoting outdated technologies.


> Elinks and others can easily update to understand a fallback attribute

Very unrealistic statement. It'll takes long time before all browsers will be able to understand new attributes.



> authors should also know their minimum browser targets and plan accordingly.

They do, indeed "nobody" uses Custom Elements and React won the audience.


> WebGL doesn't work in elinks, but I don't see people who write WebGL complaining that it doesn't work in elinks...

You are now comparing forms, lists, and tabular data friendly with screen readers with a technology used for "special effects".

Is this really the level of no graceful enhancement arguments, that elinks, a terminal based browser, doesn't render WebGL?



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