378251 - Restore closed tab adds current page to end of history

Status: RESOLVED WORKSFORME

(Firefox :: Session Restore, defect)

Description

[James Hoadley]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3

If I restore a closed tab, the history will be incorrect. It will always add the current page to the end of that tab's history, and the tab will be at the end of the history (i.e., no forward pages). For instance, if page be was current when the tab was closed:

A -> _B_ -> C -> D

When it is resotred, the tab's forward/back history will be:

A -> B -> C -> D -> _B_

Or,

A -> B -> _C_  => A -> B -> C -> _C_

Reproducible: Always

Steps to Reproduce:
1. With Session Restore operating, Open a tab
2. Navigate to any page.
3. Navigate to another, then a third.
4. (Optional) Click back once
5. Close the tab, or kill firefox
6. Restore the tab, or open firefox again.
7. Check the history of the newly restored tab.
Actual Results:  
After restore the current page will be correct, but it will appear twice in the back/forward history. Effectively the current page will be appended to the end of the history, and if the current page was at the end of the history, it will have a two entries.

Expected Results:  
As above.

I have tons of extensions which may be interfering with the correct function of this feature. I can provide a list if needed.

Comment 1

[Simon Bünzli]

> I have tons of extensions which may be interfering

If this is an extension's fault, you'll have to contact its author rather than filing a bug here. To make sure it isn't, please try to reproduce the behavior you describe on a clean profile. If you can't, this bug is WORKSFORME.

Comment 2

[James Hoadley]

OK, I've just tried to reproduce the bug on a dev machine, with only one extension running and it didn't happen, so I guess we can close this bug. I might try on mozillazine instead.

Comment 3

[James Hoadley]

FYI, it's the extension Firebug 1.04. I've notified them on their bug list.