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

My use case is this: I want to be able to extend the declarative web with new features/behaviour for existing elements. Even if I have to completely re-write the features I need for an element in script i.e. it inherits nothing except the name (not perfect, but easy, I guess).  I want to use this facility to propose new features for HTML, and I want to be able to provide a customised built-in as a polyfill for the day when the feature is implemented in some browser but not others/all.  In this way, I see customised built-in elements alleviating some of the political pressure to implement features natively which could otherwise continue to happily exist as community-supported customised built-in elements.

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