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

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

I dont know, if you work with designers much, but, if something doesnt work ___exactly___ like they designed it, they prefer to not present it all.

same for product owners: if they hear that the designer wants double or triple payment and the engineers too, because thats the additional cost of serving reliable fallbacks accross dozens of scenarios with the level of UX the designer expects, then most of the time, they just call that fallback stuff off or use "old" tech

same for users: if i cant enjoy a fallback, i either upgrade my client or dont use the app at all.

imo these statements are true for 95%+ of every webpage/web app(/even software project) that will ever hit the web/customer.

i am not against implementing a solution that provides graceful enhancement with little to no overhead and a coherent DX. also the solution must be easily enough for platform providers to implement (and ofc agreed upon). `is=""` is __not__ such a solution (imho).

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