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

it's funny people think no CEs means no JS ... I can write serer side forms with basic DOM Level 0 callbacks and the is attribute covering 100% of browsers, not only the NoJS, also the no native Custom Elements and no V0 compatible implementation.

Firefox and IE/Edge are no CEs examples. These can be also target for graceful enhancement since irrelevant on the Mobile world.

Moreover, graceful enhancement also has nothing to do with PWAs, it means the list of things I've already listed with or without JS support.

It's not black or white, and if something goes wrong on the JS side, and famous websites too have JS errors all over the console, the underlying HTML and CSS, the one used to style that button regardless the `is=""` attribute, will work without issues because are fault tolerant.

If you think `is` is meant to increase accessibility and useful only for no JS browsers, who needs to think out of the box and beyond the nose it's not probably me.

Also, about Angular, or any other framework, I don't framework much, I want to use the platform.

The platform is behind everything else and this thread is going nowhere (and I'm re-done with it).

Best Regards

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