{"id":46931,"date":"2025-03-03T15:34:13","date_gmt":"2025-03-03T20:34:13","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=46931"},"modified":"2025-03-03T15:34:13","modified_gmt":"2025-03-03T20:34:13","slug":"stopthemadness-for-safari-web-apps","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2025\/03\/03\/stopthemadness-for-safari-web-apps\/","title":{"rendered":"StopTheMadness for Safari Web Apps?"},"content":{"rendered":"

Jeff Johnson<\/a>:<\/p>\n

There’s now a Safari web extension version of Noir specifically for Safari web apps, in addition to the Safari app extension version of Noir for Safari. Of course, this solution is non-ideal, because it’s confusing to users, and you’ll notice in the above screenshot that Noir for Web Apps has to warn users—with red exclamation points!—not to enable it for regular Safari. You don’t want two different versions of the same extension running simultaneously in Safari.<\/p>

[…]<\/p>

In theory, I could follow Noir in creating a Safari web extension version of StopTheMadness specifically for Safari web apps on macOS. The question is, should I, and why? The project would be a lot of work, which I’m not opposed to, but the work needs to be worth it. Some StopTheMadness customers have requested Safari web apps support, but not a lot of customers so far.<\/p>

Besides the work involved, another problem is that Safari web apps are… weird. They have no address bar. They have no tabs. They lack some of the standard contextual menu items. They open cross-origin links in Safari rather than in the web app—unless you select Open Link in New Window! In general, the weirdness of Safari web extensions would break some of the crucial features of StopTheMadness, such as protecting ⌘-click to open links in a new tab, the Tab Rules, and the contextual menu options.<\/p><\/blockquote>\n\n

Previously:<\/p>\n