Closed
Bug 623911
Opened 14 years ago
Closed 14 years ago
First tab in stack changes when expand button is opened and then closed
Categories
(Firefox Graveyard :: Panorama, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
Firefox 4.0b12
People
(Reporter: george.carstoiu, Assigned: raymondlee)
References
Details
Attachments
(1 file, 2 obsolete files)
8.74 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b9pre) Gecko/20110106 Firefox/4.0b9pre
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b9pre) Gecko/20110106 Firefox/4.0b9pre
By opening and closing the stacked list with tabs, using the expand button, the first tab from the pile changes to the first tab present in tab view.
Reproducible: Always
Steps to Reproduce:
1.Open at least three websites in same group (ex: www.google.com, www.nasa.gov, www.cnn.com)
2.Go to Panorama and minimize group until you get stacked pile.
3.Press expand button and select www.nasa.gov
4.Go to Panorama and observe stacked pile (nasa.gov should be the first tab)
5.Press expand button
6.Dismiss opened window
Actual Results:
First tab from tab view (www.google.com) is shown as first tab in pile.
Expected Results:
Previous accessed window is shown as first in pile (our case nasa.gov).
Also, when switching for the first time from tab view to panorama and minimizing in order to obtain the stack, the first tab in the pile is not the last accessed one (in the above example www.nasa.gov).
Comment 1•14 years ago
|
||
Would this improve/be fixed by bug 616729, which should better enforce that the tab order in groups (and therefore which tab is the topmost in a stack) better sync the real tab order?
Reporter | ||
Updated•14 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•14 years ago
|
Priority: -- → P3
Comment 2•14 years ago
|
||
Bug 616729 has now landed; can you see if this is still happening, George?
Reporter | ||
Comment 3•14 years ago
|
||
Mozilla/5.0 (Windows NT 6.1; rv:2.0b11pre) Gecko/20110127 Firefox/4.0b11pre
I can still reproduce the issue.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → raymond
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•14 years ago
|
||
Attachment #510235 -
Flags: review?(ian)
Comment 5•14 years ago
|
||
Comment on attachment 510235 [details] [diff] [review]
v1
In addition to removing the topChild = null from _gridArrange(), you need to add a topChild = null to arrange() right before it calls _gridArrange(). topChild is supposed to be relatively temporary, and shouldn't survive a group getting unstacked (though I'm fine with it surviving expand/collapse).
Otherwise looks good.
Attachment #510235 -
Flags: review?(ian) → review-
Assignee | ||
Comment 6•14 years ago
|
||
(In reply to comment #5)
> Comment on attachment 510235 [details] [diff] [review]
> v1
>
> In addition to removing the topChild = null from _gridArrange(), you need to
> add a topChild = null to arrange() right before it calls _gridArrange().
> topChild is supposed to be relatively temporary, and shouldn't survive a group
> getting unstacked (though I'm fine with it surviving expand/collapse).
>
Put topChild = null right before it calls _gridArrange() would simply bring back the bug. I've moved the topChild = null to the else block in _gridArrange() so topChild would get cleared when a group is not stacked.
Attachment #510235 -
Attachment is obsolete: true
Attachment #510500 -
Flags: review?(ian)
Comment 7•14 years ago
|
||
Comment on attachment 510500 [details] [diff] [review]
v1
Good call
Attachment #510500 -
Flags: review?(ian) → review+
Assignee | ||
Updated•14 years ago
|
Attachment #510500 -
Flags: approval2.0?
Comment 8•14 years ago
|
||
Raymond, please make sure that this bug doesn't make the bug 633074 regression worse... just want to make sure, as this touches similar code paths.
Assignee | ||
Comment 9•14 years ago
|
||
(In reply to comment #8)
> Raymond, please make sure that this bug doesn't make the bug 633074 regression
> worse... just want to make sure, as this touches similar code paths.
I am certain that it would make the bug 633074 regression worse.
Assignee | ||
Comment 10•14 years ago
|
||
(In reply to comment #9)
> (In reply to comment #8)
> > Raymond, please make sure that this bug doesn't make the bug 633074 regression
> > worse... just want to make sure, as this touches similar code paths.
>
> I am certain that it would make the bug 633074 regression worse.
Oops! I mean it would not.
Assignee | ||
Comment 11•14 years ago
|
||
Comment 12•14 years ago
|
||
(In reply to comment #10)
> (In reply to comment #9)
> > (In reply to comment #8)
> > > Raymond, please make sure that this bug doesn't make the bug 633074 regression
> > > worse... just want to make sure, as this touches similar code paths.
> >
> > I am certain that it would make the bug 633074 regression worse.
>
> Oops! I mean it would not.
lol good. That's what I thought. :)
Comment 13•14 years ago
|
||
Comment on attachment 510500 [details] [diff] [review]
v1
low footprint, has tests, improves behavioral consistency in Panorama -> a+
Updated•14 years ago
|
Attachment #510500 -
Flags: approval2.0? → approval2.0+
Comment 14•14 years ago
|
||
Attachment #510500 -
Attachment is obsolete: true
Updated•14 years ago
|
Keywords: checkin-needed
Comment 15•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Flags: in-testsuite+
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b12
Reporter | ||
Comment 16•14 years ago
|
||
Mozilla/5.0 (Windows NT 6.1; rv:2.0b12pre) Gecko/20110215 Firefox/4.0b12pre
Issue no longer present.
Status: RESOLVED → VERIFIED
Updated•9 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•