745541 - Clicking a bookmark from the bookmarks toolbar WHILE opening a new tab will change to the bookmarked site without being able to return to the originally targeted site ('Go back one page' button is greyed out).

Status: NEW

(Firefox :: Bookmarks & History, defect, P5)

Description

[Christoph Schulz]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0
Build ID: 20120312181643

Steps to reproduce:

I opened a new tab (via right click -> open link in new tab) and *WHILE* (crucial!) the targeted site (lets call it www.abc.com) is being connected to, I hit a bookmark button from another site (lets call it www.xyz.com) that is listed in the bookmarks toolbar.


Actual results:

Firefox discontinued connecting to www.abc.com and opened www.xyz.com in the new tab instead (correct behavior) BUT it does NOT allow returning to www.abc.com (which was targeted in the first place) via the 'go back one page' button, which remains greyed out as if there had never been a previously targeted site. So just because the connection to the originally targeted site was never established, Firefox behaves as if it had never been targeted at all. 


Expected results:

The 'go back one page' button should not be greyed out, one should be able to return to the previously targeted site as is the case whenever one waits until the originally targeted site is loaded and THEN hits a bookmark button. In this case, the 'go back one page' button is clickable. If this behavior is intentional (= "not a bug but a feature", an assumption supported by the fact that this behavior is relatively new to Firefox so it seems almost intentionally included) I seriously doubt the logic behind it. 'Going back one page' should always refer to the previous action of the user and not to whether a connection to the previously targeted page had been established or not.

Comment 1

[Marco Bonardo [:mak]]

likely valid but minor, it's likely the page is not yet registered in session history when we start loading the next page, depending on dns resolution and network... I suppose we may not be willing to spend resources to actually try to fix it, due to low benefit.