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

There is a lot aggressive agreement going on here.

The most basic point - which is where I think most people, outside of WebKit devs, seem to agree - is that we want an ability to use and build on top of the un-replicable behaviours of some native HTML Elements.

The rest of the arguments - which cases are useful / possible; the syntax (is=""); whether it should be inheritance or composition; etc. - are all fine but really aren't worth getting worked up about while there are browser vendors not intending to implement _any_ way of achieving the core premise.

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