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

This is just a reminder that [my V1 polyfill](https://github.com/WebReflection/document-register-element) forces `is="native"` feature in browsers that don't support it, and it uses it natively where available.

I think _we_, developers, will find a way to implement `is="native"` feature in a way or another; I just wish _they_ (browser vendors) will stop pushing back instead of understanding its use cases that are simply or impractically impossible to reproduce otherwise.

`template`, `tr`, `body`, and even `html` are just few examples of what we're missing as extending possibility for the whole Web platform, present and future.

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