Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509)

Some things are complex to implement, but this particular change doesn't seem to be.

Would you mind kindly pointing to the complexity and impact that make it non-desirable?

Is it because if the element isn't registered (i.e. with JS turned off) that the browser won't know to at least render a fallback `<button>`? I think that's perfectly fine, because without JS the app probably won't work anyways, and I'm willing to bet that most people who will write JavaScript-based Custom Elements won't care if the app doesn't work with JS turned off. The [Nike](http://www.nike.com/us/en_us) website doesn't work with JS turned off, and they care. Most people won't care. Developers who do care can just as easily use `<noscript>` and place a `<button>` in there, which makes much more sense.

What other reason might there be?

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