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

> I've said this fifteen different ways already, but what the heck. So <button is="super-button"> is still a button and will work as a button. OK - great if for some reason the runtime can't deliver the <super-button> then at least it's still a button. But if the designer went through the trouble to use custom elements then she's probably in the pool where several other custom elements that communicate and perform services are being used as well (Most of us don't just throw a button on a page and call it a day). So while it's true that the button is fault tolerant, the rest of the app is not. If you are driving over a bridge where 20 feet of the cross section is missing do you care that it's impossible for the screws holding the bridge up to rust?

Unless I want a website that both looks great in evergreen browsers and yet still 'functions' (even if not as pretty) in older browsers or text browsers or screenreaders (without duplicating the content and thus having some screenreaders duplicate what they read) and etc... etc... etc...

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