Posted by Steve Zimic on August 10, 2013 at 9:39 AM
This is not a big deal but something that has recently cropped up. I've noticed that after clicking on an image in a gallery, I can't go back to the index unless I hit the 'back' button twice. This is happening on all my macs and versions 4,5 and 6 of Safari. Firefox however works without a hitch.
Posted by Ken Smith on August 10, 2013 at 10:09 AM
Agree...same w/my Mac using Safari.
Posted by Keith Bauer on August 10, 2013 at 11:04 AM
Ditto. Seeing the same behavior on my Macs.
Posted by Ian Wolfenden on August 10, 2013 at 11:12 AM
Ditto on my Mac. This is only the case with NPN navigation - on other sites the back button works ok
I am seeing this in latest version of FireFox. I also see it in IE10, unless I switch to 'Compatibility Mode'. When I do that the back button works as it should.
--P
Posted by Jim Erhardt on August 11, 2013 at 7:55 AM
Keith, what keeps changing is browser behavior with each new version. It's a moving target, and there are at least four of them (IE, Firefox, Chrome and Safari) that we now have to monitor. Even the simplest of changes/additions (such as the recent addition of the SM Buttons) results in weeks of emails reporting problems, trouble shooting, etc. Get the problem fixed in one browser, and create a new problem in another.
While most despised the near monopoly IE once had, it sure made life much simpler for webmasters.
Posted by Steve Zimic on August 11, 2013 at 8:30 AM
Jim,
I hear you re: 'moving target' - must be a pain. Not sure if you'll even bother to solve this issue since it's no biggie, but here's something I found that might help pinpoint it. So I hit the back button twice and go back to the index. I then hit the forward button once and it goes to the image/post previously viewed. I now hit the back button only once and it does go directly back to the index. Interesting?
Posted by Jeff Lewis on August 20, 2013 at 2:31 PM
Another kibitz - this is likely from the specific javascript code from jaaju.com for the sharing buttons - when they load the buttons under the picture they are using an "iframe" element to place them, and they are most likely updating the "src" attribute of the iframe AFTER the main page loads and the iframe is created. I think pretty much always updating a src element like that after creation adds an entry to the browser history.
IE in compatibility mode doesn't load the iframe, or buttons, so the back issue doesn't occur.
I would think this is definitely something they need to have an answer for in a beta test.
Discussion
12 replies--P
While most despised the near monopoly IE once had, it sure made life much simpler for webmasters.
I hear you re: 'moving target' - must be a pain. Not sure if you'll even bother to solve this issue since it's no biggie, but here's something I found that might help pinpoint it. So I hit the back button twice and go back to the index. I then hit the forward button once and it goes to the image/post previously viewed. I now hit the back button only once and it does go directly back to the index. Interesting?
IE in compatibility mode doesn't load the iframe, or buttons, so the back issue doesn't occur.
I would think this is definitely something they need to have an answer for in a beta test.
Jeff
I am still seeing this in IE 10 (normal mode) on 8/25.
-p