Closed
Bug 626269
Opened 14 years ago
Closed 14 years ago
Tabs not seen after going to and back from Private browsing mode, plus not in line with Panorama informations on groups
Categories
(Firefox Graveyard :: Panorama, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 594644
People
(Reporter: l.barchan, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b9) Gecko/20100101 Firefox/4.0b9 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b9) Gecko/20100101 Firefox/4.0b9 After entering the Private Browsing mode and leaving it back to normal mode the last active tab only is displayed from the last active tabs group. If I close it, the other group is displayed. If I go back to Panorama and back, everything is restored. Reproducible: Always Steps to Reproduce: 1. 2 tab groups, A and B, visible in Panorama mode. Three tabs in group A: A1, A2 and A3. One tab in group B: B1. Group A is visible, and tab A3 is active. 2. Switch to Private Browsing mode. A new empty tab is observed (as expected). 3. Switch to Normal Browsing mode. Actual Results: Only tab A3 is visible and active, no more tabs seen in the window at all. Expected Results: Seeing tabs A1, A2 and A3, with tab A3 being active. To resolve the problem there are 2 ways: - (destructive) If I close tab A3, the browser switches to displaying tab B1. Tabs A1 and A2 are still not forgotten, I can switch to them using Panorama mode. - (non-destructive) If I switch to Panorama mode, I can see both groups as they were, selecting tab A3 brings everything back to normal initial state (as in Step 1 of the "How to reproduce" sequence).
Comment 1•14 years ago
|
||
Unfortunately this was a bug that was not fixed in time for beta 9, but will be in the next one.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Component: Private Browsing → TabCandy
OS: Windows XP → All
QA Contact: private.browsing → tabcandy
Resolution: --- → DUPLICATE
Version: unspecified → Trunk
Assignee | ||
Updated•8 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•