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.

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

Elinks and others can easily update to understand a fallback attribute, and
authors should also know their minimum browser targets and plan accordingly.

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

On May 16, 2017 7:52 AM, "Oliver Hoff" <notifications@github.com> wrote:

Browsers that are completely unaware of Custom Elements would indeed ignore
it. and elinks should be updated to allow unknown tags with known fallback
behavior.

But then you can modify the proposol to use Element composition insteadof
fallback attr

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/w3c/webcomponents/issues/509#issuecomment-301807607>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AASKzmPIN1xRMDhG4VXSxw0KqI963MzHks5r6bgmgaJpZM4Iq2sA>
.


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