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

> So this isn't being implemented for ideological reasons, is that right? After 8 years seems safe to say that `is=""` has been adopted by everyone else. Safari is the new IE here.

Worse than that, because Apple has neither proposed nor implemented a viable alternative.

The most recent and perhaps most patronising development yet in the saga was locking their [own feedback ticket](https://github.com/WebKit/standards-positions/issues/97) as "off topic" after months of alternately ignoring and rejecting the overwhelming community response regarding the value of customized built-in elements.

> seems to me that anyone seriously suggesting there are "better" methods than simple inheritance hasn't tried implementing any of this stuff in real-world apps of any real complexity. IMHO of course.

There's a great article from Brian Birtles [here](https://birtles.blog/2024/01/06/weird-things-engineers-believe-about-development/) about how divorced browser engineers are from real-world web development challenges.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/509#issuecomment-1890859813
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/509/1890859813@github.com>