Closed Bug 324787 Opened 19 years ago Closed 19 years ago

New tabs don't remember the "back" history

Categories

(Firefox :: Tabbed Browser, defect)

x86
Linux
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 18808

People

(Reporter: thomas, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; da; rv:1.8) Gecko/20051202 Fedora/1.5-0.fc4 Firefox/1.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; da; rv:1.8) Gecko/20051202 Fedora/1.5-0.fc4 Firefox/1.5 If I open a link in a new tab, the new tab greys out the back-button, instead of copying it from the tab it was opened from. Reproducible: Always Steps to Reproduce: 1. Get some stuff in your "back history" 2. Open a link in a new tab Actual Results: New tab has no "back history" Expected Results: New tab should copy the "back history" from the "parrent" tab, just as if it wasn't opened in a new tab, but the link was clicked normal.
This is intended behaviour. Each tab maintains their own history because the most common user pattern is to open a link in a new tab, read it and then close it to return to the parent tab. The functionality you are after is most likely one to be left to an extension.
(In reply to comment #1) > This is intended behaviour. Each tab maintains their own history because the > most common user pattern is to open a link in a new tab, read it and then close > it to return to the parent tab. But if they by accident closes the parent tab, then they are absolutely lost, and may use 5-10 minutes to return to the same page. I don't see that it hurts anybody who closes the child tab after reading it, that it has a history.
(In reply to comment #2) > But if they by accident closes the parent tab, then they are absolutely lost, > and may use 5-10 minutes to return to the same page. I don't see that it hurts > anybody who closes the child tab after reading it, that it has a history. The links are still in your Go-menu or in your history sidebar.
See also bug 18808.
This bug will be fixed by bug 18808. *** This bug has been marked as a duplicate of 18808 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.