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

@oleersoy

Would you mind re‐explaining to me what do you have a problem with? I seem to have lost it in all the discussion…

I see you don’t like `is`, but do you think it’s important to be able to extend built‐in elements? If so, what do you propose as a solution? One can’t simply say “allow `<my-tr>`”, for the multiple problems it brings (as stated several times already).

You may feel it’s unnatural (I feel so too), but it’s the best working solution we currently have.

Honestly, I’m starting to agree with @rniwa and Apple more and more that it might be better to simply not allow extending built‐in elements; at least not in the same way we extend custom elements.

(by the way, @oleersoy, you seem to think @WebReflection is from the W3C, which is simply not the case; Heh 🙂😜😝😝)

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