[Safari] Problem with browser back button

I'm running Mavericks and Safari 7.1.7 and have the blank page are using the back button as described in other posts.

Using the "Develop" menu, I looked at some error messages in the console. They all complained about a CSS token. The active web content that showed 40+ extremely long lines without spaces. It was mostly Javascript.

So I disabled Javascript using the Develop menu and, so far, every click of the back button has worked while using Google search.

It's more information, but not necessarily useful as many sites, including this one, require JavaScript.

lstroud wrote:

I may have resolved mine by changing the search engine, searching, then changing it back to google. Perhaps that clears a cache somewhere.

I tried this. Immediate result is that this has resolved my problem. OS X 10.10.4 Safari 8.0.7 MacBook Pro (Retina, 15-inch, Late 2013). I changed to Yahoo, searched, selected a link, changed back to Google and I have not had the problem reoccur yet. I will follow up if the problem returns.

I noticed in the system log, this error message when the event occurred (I have not correlated it to make sure this error does not happen any other time):

8/13/15 9:06:06.093 AM Safari[1663]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 3. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.

Does this mean that some configuration file is corrupt? Any idea how to find out which one?

Just to add to the list of people with issues: I have also been experiencing this problem for a quite some time now.

Seems like there are some temporary workarounds but nothing that solves the problem. It's frustrating for those that google frequently (developers and such) as it slows down the workflow many many times a day.

Brand new out of box iMac, no extensions, no big cache or anything yet cluttering up system (new as in brand new)...and can't go back to Google results. 😟

There has to be some bug, and with 4 pages of problems when will we get a real response from a "Genius" to this annoying issue! I guess I'll be loading up Firefox and Chrome to my new machine, since it came complete with the old problems....

This bug still exists in 10.10.5 so obviously Apple are completely stumped on this haha! Or I suppose its possible they are trying to sabotage Google and make us move to another Search as some have done by switching to Bing. I'll switch to Bing and give that a try and if the results aren't good enough I suppose I'll need to go back to Firefox.

Sorry Tom, Adblock is not the problem. Follow the instructions a few posts back and change your google settings. That works. This is a Safari problem as it doesn't happen with any other browser, but as mentioned previously, it is a waste of time to complain here.

Although disabling Instant results resolves the problem, that does not make this a Google issue. Google Chrome, Mozilla Firefox and other web browsers do not have any problem with that setting enabled. Safari is not handling something correctly. Apple needs to fix this because Instant results are convenient.

Agreed. It is an Apple problem as Safari is the ONLY browser having the problem. Further, Safari worked just fine with Instant Results until one of the more recent updates. Changing Google settings is a workaround until Apple solves the problem. I'm not holding my breath.

This problem just started happening for me last week. I have 3 separate google accounts and I was logged out of all of them. When I tried to go to the google sign-in page my browser would just hang. I quit safari, re-loaded and then logged into one of my google accounts. The problem of the back button going to a blank page no longer happens.

I've submitted the issue here http://www.apple.com/feedback/safari.html worth a shot I guess!

Hello !

Mapple89

i found article Safari 9 (El Capitan): If an encrypted webpage doesn’t open

Same problem here.

deleting cache.db did not work.

Remove All Website Data may have worked. time will tell.

I spoke too soon. There's no change. The problem still exists.

me too

even had it happen after I signed in to this forum and tried to go back to post this note :-)