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

@oleersoy in this case you have quite a different situation:

  1. custom builtins were already possible in V0
  2. libraries shipping them already made everyone happy and are successful stories (Polymer, AFrame, others)
  3. specifications in V1 also defined them
  4. Chrome already shipped `is="..."` and AFAIK Firefox is following
  5. polyfills implemented that already and are successful stories too (Polymer, AFrame)
  6. you are **really** free to not use `is="..."` in all cases where it's not mandatory (not `LI`, `TD`, `SELECT`, `OPTION`, etcetera)

Custom Elements builtins are needed on the Web and indeed as soon as available tons of developers used those and it worked, as ugly as it looked.

So many things on the Web work, as ugly as these look, and new API that get replaced are also part of the Software story. In this case nobody came up with anything implementable in the next 5 years so you gotta be pragmatic and move forward, IMO.


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