MacOS – Safari on MBP keeps running extensions for the ‘first’ time on startup

macossafarisafari-extensions

Strange problem – I recently purchased a MacBook Pro, recently updated to the latest OSX and I have an issue in Safari where when I install an extension (doesn't matter what extension) Safari will keep loading its "first time installed" dialog, every time I start safari rather than once, when the extension is installed.

It is driving me crazy – I have tried it with another user on the same mac – I can't reproduce the problem. I have tried it with multiple extensions installed, and a single one, every extension I have installed (1Password, Amazon, Ad-block) recreate this problem.

I have uninstalled extensions, deleted preferences, etc…

Any ideas anyone?

I have had a look at this question (which is the opposite of what is happening to me): Installed Safari Extensions disappear after restarting Safari
I tried deleting extension-related keychains, and changing permissions on the Safari Extensions List but to no avail…

Best Answer

Soon after writing the question, I realized that even with no plugins installed, I had the Welcome page appear, which changed what I googled for. That helped me find:

https://discussions.apple.com/thread/6663182?start=0&tstart=0

sudo find ~ $TMPDIR.. -exec chflags -h nouchg,nouappnd,noschg,nosappnd {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-

Further explications at Render's request:

So let's assume this code on all pages:

$(document).ready(function () {
    alert('test');
}

And this sequence of actions:

open page-1.html
open page-2.html
Go back
Go forward

Safari won't show the alert after step 3 and 4, so I the onLoad event is not fired and the page .js continues the execution from where it left off when you navigated away from the page.

Also in the current version 6.0.3, having 1password extension (3.9.14) seems to have no effect over this behavior.

Hope that helps. This shouldn't matter in most cases, it's only when you write bad code (like it did) it will bit you in the arse :)

Best Answer

Related Solutions

Better tabs management in Safari 6.x

MacOS – Safari 6 refreshes when I go back

Further explications at Render's request:

Related Question