Now that we've removed the drop down arrow from the back/forward buttons, we need to make sure that users won't get into a situation where they are immediately redirected when they hit back (making it impossible to go back 2 steps). The back button should carry the user past pages that quickly redirect.

Nominating for blocking since this is a somewhat significant usability problem with one of the most important controls in the browser.

(In reply to Alex Faaborg [:faaborg] (Firefox UX) from comment #0) > Now that we've removed the drop down arrow from the back/forward buttons, we > need to make sure that users won't get into a situation where they are > immediately redirected when they hit back (making it impossible to go back 2 > steps). The back button should carry the user past pages that quickly > redirect. I think that, after a swift redirection, the Back button has to be enabled and the previous page has to be recorded in Firefox' history and in the tab's navigation history. I am discussing the reasons why here : https://bugzilla.mozilla.org/show_bug.cgi?id=606286#c33 Why a swift redirection would make it impossible to go back two steps ? I can long-click on the Back arrow and select the entry which is two steps back. But maybe you also want two simple clicks on the Back button to go two steps back. In this case, I understand and I give you two solutions : 1. Before clicking Back, cut the Internet connection. For example, turn off AirPort or unplug the network cable. 2. In Firefox' Preferences, tick “Warn me when websites try to redirect or reload the page”. Let's even make this pref ticked by default. And ensure that it works in all cases. Which is currently not true, although Firefox' help says : “When this preference is enabled, Firefox will prevent websites from redirecting you to another page, or automatically reloading.”

I think the problem you have is not in fact in the Back button, but in the (too) quick redirect.

Continuing discussing these issues in request bug 606286 and request bug 687300.