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

@WebReflection

Well, I don’t think we should just stop in time, I just don’t want bad, unthoughtful, and non‐future‐proof APIs to be welded into the Web forever.

> […] specially when `is=""` solution,as ugly as it is, already worked for the last 2 years and keeps working without problems polyfilled.

I said it before, and I’ll say it again: it “working” doesn’t mean it’s something good from a language‐design/API‐design perspective.

By the way, I’m not saying I dislike `is` (I do like it, and hope that it stays), I’m just disagreeing with your arguments for it.

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