[Webkit-unassigned] [Bug 182671] Implementation (or not) of customized builtins (is="" attribute)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=182671

--- Comment #21 from Andrea Giammarchi <andrea.giammarchi at gmail.com> ---
Once again, and to whom it might concern, the less than 2K poly can land either feature detected [1] or through exclusion the browser is neither Chrome nor Firefox [2].

All metrics for SEO score 100% and performance are not affected for all browsers but also extremely fast on WebKit based devices.

Move the polyfill from CDN to same site and let's use it instead of keep telling them we need built-in extend, shall we?

It's clear the situation and limitations have been stuck forever and won't change until Web developers understand there's nothing to wait for and things can work out of the box for everyone.

Please note all approaches are based on a feature no ShadowDOM will ever enable, as it is a script tag in the head of an HTML file that's extended to understand if the functionality is available or not ... this is just yet another scenario builtin extend demonstrate their superiority: head elements otherwise impossible to hook into through the regular Custom Element Registry.

Another missing opportunity for the future of the Web.

[1] https://codepen.io/WebReflection/pen/xxWaVKo
[2] https://codepen.io/WebReflection/pen/bGvYdVw

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220811/db3a46de/attachment.htm>