Bug 231419 – REGRESSION (Safari 15.1): The WordPress Customiser does not load: bind must be called on a function

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: JavaScriptCore

[Eduard Comănici]

Created attachment 440589 [details]
Errors shown when accessing the wordpress customiser

Install a fresh copy of WordPress and attempt to access the customiser. Notice it stops executing the JS. This did not happen in Safari 15 (Monterey Beta 7), it started happening in Safari 15.1 (Monterey Beta 8 & 9).

This stops me completely from using Safari, because I rely on accessing the WordPress customiser on a daily basis.

Here's more information -- https://generatepress.com/forums/topic/customization-options-gone-across-multiple-sites-gp-3-0-4-gp-premium-2-0-3/page/2/

I have also attached a video.

[Radar WebKit Bug Importer]

<rdar://problem/84103658>

[Justin Michaud]

Hi Eduard,

Thank you for taking the time to submit this bug, we really appreciate it. It appears that this issue has actually already been fixed, and so we just need to wait for the fix to land in a new build. I will check again once a new build is released.

I haven't tried building with and without this patch to be certain, but I have verified that the issue was fixed some time here: https://trac.webkit.org/log/trunk/?mode=follow_copy&rev=283560&stop_rev=283556. https://bugs.webkit.org/show_bug.cgi?id=231202 seems to be the only possible culprit, and the issue does not reproduce past it. For this reason, I am marking this bug as a duplicate of that one. 

Thanks
Justin

[Justin Michaud]

*** This bug has been marked as a duplicate of bug 231202 ***

[Eduard Comănici]

Hey Justin. That's great news! Safari is my primary web browser and I swear by it. I wonder if this fix will land before macOS Monterey gets released, since otherwise, it would really hurt my workflow.

[Yusuke Suzuki]

(In reply to Eduard Comănici from comment #4)
> Hey Justin. That's great news! Safari is my primary web browser and I swear
> by it. I wonder if this fix will land before macOS Monterey gets released,
> since otherwise, it would really hurt my workflow.

Apple does not comment on future products or releases.
But it is already shipped in Monterey. (I can comment on that since it is already shipped).