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

too bad GitHub is half down today so you cannot see demo pages in elinks ... will ping you back once up and running again so you can understand the power, simplicity, and beauty of custom elements built-ins.

Also, after years working with Custom Elements in general:

  * the inheritance of builtins is superior, you get everything the standard/semantic element has to offer
  * multiple button with different classes are not an issue, no more than multiple custom elements that would like to be a built-in (and surely less)
  * there are (virtually) less DOM nodes to handle, and built-ins are easily well optimized in core
  * there is less to parse and UI works out of the BOX, you don't need to wait for definitions

I actually believe if the Custom Elements story was born extending builtins only, instead of a pseudo empty HTMLElement with a complex and unpolyfillable Shadow DOM the Web would be in a way more advanced way.

Instead, we keep discussing this thread ... but hopefully my latest poly that weights < 1K and works down to old IE (after optional polyfill for Custom Elements) would help moving forward.

If only we could have decorators to easily enrich classes instead of being stuck with single inheritance model it'd be so fun creating components and apps.

/rant

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