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

It's not different.  People who started using default exports thought it was a good idea.  It made it into the specification and then tons of people used it and thought they were doing a great job.  Now we see that it hurts our ability to refactor code and limits tree shaking, thus every product produced with default exports is less maintainable and heavier in terms of bandwidth than it needs to be.

The `is` attribute has the same effect.  Everyone that uses it has to start making special considerations for their css.

1) Is it a `input[is=fancy-input]` selector or
2) a `fancy-input` selector in the event that the custom element was created by the custom element API?




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