Thread title pretty much says it. I’ve recently noticed that I can’t navigate back on Amazon’s website using the ‘back’ arrow of the IE9 browser. I don’t have this issue with any other website. It’s most annoying.
Many shopping sites do this. I think it is to compensate for sloppy programming. For example, if you go back and change your order, their computer might not realize that you’ve changed your order, but might think that you’re entering an additional order. Stuff like that. Disabling the “back” button prevents some of those things.
I run onto sites sometimes where the back button doesn’t work, and it doesn’t always seem to be shopping sites. I’ve found, however that by using the “recent pages” arrow beside the back/foreward buttons you can back up by using the pull-down menu. For some reason that always seems to work even where the back button doesn’t. FWIW.
SS
It seems bizarre on a site where being able to browse is important. I almost never buy the first book I look at, but would like to be able to get back to it with a couple of clicks, if necessary.
On sites like that, I almost always use middle-click to open the next window in a new tab, so teh old one still stays there. (I use Firefox, but I think this works in IE too.)
In FF I combine this with use of the “Back to Close” add-on and the mouse side button set as a back button. This makes things even easier, but it is not essential.
The reason it works that way is that you bypass the redirect that simply hitting the back button sets up.
Some sites have multiple layers of redirects, and when I discover those sites they go into my list of restricted sites.
To explain further, the simplest way to disable the back button is through redirects. When you click a link on Page A, it doesn’t take you directly to Page B where you want to go, but to Page C, which is set up to immediately forward you to B. So when you’re on B and hit the back button, that takes you to C, which immediately sends you back to B. With the dropdown, though, instead of going back one page at a time (to C), you can go back multiple pages, to A.
Since I can’t even understand the explanation, it’s time for an email to Amazon to complain.
My FF5 back button works just fine on Amazon.
Back button works fine in Chrome too!
Yeah, but all modern browsers compensate for this by asking you whether you want to resubmit the information.
Combined with the fact that Chrome and Firefox work correctly, I’m going to assume it’s an accident. Firefox has this problem in one of the betas of Firefox 4. It has to do with how the browser history is processed. Sometimes you get two versions of the same page–I think because the code refreshes the page or something.
IE9 is new. Did you notice the problem around when you installed it? I’m using IE8 and the back button works just fine at Amazon.
In light of the above posts, you may be on to something. I sent an email and they promised to look into it, but it’s probably a MS glitch (big surprise).
Which is not really a solution. What exactly is getting resubmitted? From the user perspective there is no way to know.
The problem is that browsers were designed for a stateless display of information and we are trying to use them for processes that are inherently full of state. It’s a complete mismatch. What does it mean to have a link to a page that is dependent on the state at the time it was generated and that the state has now changed? I don’t think it makes much sense at all.