Closed
Bug 214905
Opened 21 years ago
Closed 21 years ago
back to previous group of tabs conflicts with page history navigation
Categories
(SeaMonkey :: Tabbed Browser, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mozilla.jgvons, Assigned: jag+mozilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030802 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030802 After opening a bookmark group, Mozilla now replaces the current set of tabs instead of just adding them, and the back button brings back the previous group. However, if after opening the bookmark group, I click on a webpage link in one of the tabs, I can no longer go back to the previous group: for the current tab, the back button now takes me back to the previous page, and the "Group of Tabs" is no longer available. Moving to one of the other tabs doesn't help, the "back" button is now grayed out. Reproducible: Always Steps to Reproduce: 1. open a group of bookmarks 2. click on a link on one of the loaded pages (don't control-click: make it open in the same tab, _not_ a new one!) Actual Results: Can no longer use the back button to go back to the previous "Group of Tabs", causing data loss. Expected Results: Not sure what to expect: with the changed behavior related to the opening of groupmarks (see bug 209360), a concept of tab-set history is introduced, and mixed with the existing page-history navigation. For this to work right, the tab-set history should probably be managed by a separate button or something.
Reporter | ||
Comment 1•21 years ago
|
||
Oops, the bugid I referred to should be 203960 instead of 209360...
This is by design and after a lengthy discussion this was chosen as the default behavior. However the PREFERENCES panel offers a way to switch back to the old behavior: PREFERENCES - NAVIGATOR - TABBED BROWSING. Marking INVALID
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•