{"id":29136,"date":"2020-06-03T15:59:15","date_gmt":"2020-06-03T19:59:15","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=29136"},"modified":"2022-07-14T15:07:08","modified_gmt":"2022-07-14T19:07:08","slug":"unable-to-enable-safari-extensions","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/06\/03\/unable-to-enable-safari-extensions\/","title":{"rendered":"Unable to Enable Safari Extensions"},"content":{"rendered":"

Jeff Johnson<\/a> (tweet<\/a>):<\/p>\n

In macOS 10.15.3, Apple introduced a bug that can prevent you from enabling or disabling Safari extensions. In order to enable or disable an extension, you must click the checkbox next to the extension in the Extensions pane of Safari Preferences. […] When the bug occurs, however, then clicking the checkbox does nothing: the checkbox doesn’t get checked, and the extension doesn’t get enabled either.<\/p>

[…]<\/p>

I believe that this Safari bug was introduced by Apple in a bungled attempt to prevent extensions from getting enabled via “synthetic clicks.” […] In theory it may be a good idea for Apple to prevent synthetic clicks in this case, but in practice the code that Apple shipped here was buggy and caused more harm than help. Safari incorrectly identifies real user clicks as fake synthetic clicks, preventing users from enabling their installed Safari extensions.<\/p>

[…]<\/p>

The other issue here is the lack of a visible error message for the user. I found a message buried among thousands of other unrelated messages in Console log, but no normal Safari user will ever see that. There ought to be a warning in the Safari Preferences window. Silent failure is a security failure. If an unauthorized process were in fact trying to secretly enable Safari extensions, shouldn’t the user be made aware of that immediately?<\/p><\/blockquote>\n\n

It still happens in macOS 10.15.5.<\/p>\n\n

Rob Griffiths<\/a>:<\/p>\n

\n

Here’s the bug I filed<\/a>: Safari’s Extensions prefs panel behavior can confuse users<\/p>\n

In 10.15, Apple prevents users from enabling Safari extensions if they’re running an app with a full-screen invisible window. But with zero feedback, it just looks broken.<\/p>\n<\/blockquote>\n\n

Rudy Richter<\/a>:<\/p>\n

\n

its a constant complaint by users of 1Password that they can’t click it<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n