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

> So the goal is to have a 10+ year old client to be able to display something when given a document authored with recent technology in mind?

**No**. The goal is graceful enhancement, which means the following:

  * you're able to show a form before the component is asynchronously loaded
  * you re able to chose a select before its component is asynchronously loaded
  * you are able to compose web components through their Promise based API and load them on demand without blocking most basic features of the Web already compatible with every browser and screen reader and gaming console as well as spaceships
  * you are able to offer a basic functionality that enables users before they'll have some JavaScript error because the Custom Elements wasn't transpled properly
  * you are able to ignore Custom Elements if these add non essential values to the already available native component in emergent markets with poor 2G connections and not much data
  * you are able to promote at distance anything already semantically understood from the browser

I hope it's now a bit clearer why the ability to upgrade native element is important.

We've all done that already and we will do that regardless what WHATWG says (again, React as example) but having a platform way to do that would be an excellent compromise for everyone.

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