[Webkit-unassigned] [Bug 258282] New: Safari TP172 broke custom element built-in polyfill by making form properties non deletable

[bugzilla-daemon at webkit.org]

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

            Bug ID: 258282
           Summary: Safari TP172 broke custom element built-in polyfill by
                    making form properties non deletable
           Product: WebKit
           Version: Safari 16
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mic.gallego at gmail.com

Hi,

Apple never wanted to implement the full custom element spec with the built-in element extensions. Devs had to rely on polyfill for that (especially the excellent ungap/@custom-elements: https://github.com/ungap/custom-elements)

This has worked well for ages, but starting from Safari TP172, the polyfill broke. After discussing with polyfill authors it appears that Safari made some properties non deletable (https://github.com/ungap/custom-elements/issues/18).

This shows how important it is for Apple to fully implement the spec here (even if they don't like it), as relying on a polyfill can cause such issues. We have thousands of stores relying on this that will suddenly break on next version of Safari.

Apple refusing to implement the full spec is one thing, but at least Apple should ensure to not break popular polyfills, as thousands of websites are relying on this.

Can something be made to at least revert the change that broke the polyfill, and re-consider again the implementation of customized built-in?

-- 
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/20230619/133c1fe7/attachment.htm>