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.

`is` may be awkward, but it is of no matter at all when elements are being created dynamically in code anyway (`new CustomElement()`).  OTOH re-creating the full functionality of input elements just for a small tweak is absurd.  Or having to fall back to the old ways of shadowing actual input elements, proxying events and attributes/properties/etc... "mutation observers" really? Bleh. All just workarounds that extending built-ins gets rid of.  Most (if not all) of the basic "custom input element" examples I've seen to date end up wrapping an actual input in the shadow DOM.  Great improvement... yea!

Sorry, but 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.

Regards,
-Max



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

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

Received on Sunday, 14 January 2024 02:14:01 UTC