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

Last thoughts:

> The core reason we are using is is that we are dealing with user clients that may or may not support the custom element API. All UX / Experience designers will tell you to keep the user experience as consistent as possible across devices / platforms. Using the is attribute with this goal in mind has to add complexity in terms of markup, css, and API usage.

that is exactly why `is="..."` is superior to everything else. It works everywhere already, you can style it already, maybe the form won't be too fancy but its data will be submitted.

I think you misunderstood the benefits of the `is="..."` specially in terms of UX. Please read again this **entire** thread.

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