Closed
Bug 625955
Opened 14 years ago
Closed 13 years ago
Group's columns value is not reset correctly after tabs are removed.
Categories
(Firefox Graveyard :: Panorama, defect, P4)
Firefox Graveyard
Panorama
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 10
People
(Reporter: mitcho, Assigned: luyunxie)
References
Details
(Keywords: polish, Whiteboard: [visual][good first bug])
Attachments
(2 files, 2 obsolete files)
(deleted),
video/ogg
|
Details | |
(deleted),
patch
|
ttaubert
:
checkin+
|
Details | Diff | Splinter Review |
When the second to last tab is removed from a GroupItem, the Group Item continues to be rendered as if there are two tabs and therefore must have two columns.
While mostly visual in nature, it seems like this may be one part of bug 622872 (blocker).
Comment 1•14 years ago
|
||
I believe that the original design was that above a certain width, a lone tab would take only half the available width of the group. Otherwise you end up with a huge tab that fills the group entirely. By providing that extra space, we invite more tabs to be dropped in, and we avoid having the group just be an extra frame around the tab. Of course below a certain width, it made sense for the tab to fill the group, other wise it would be too small.
It appears that the code that did that has eroded such that it kind of does it sometimes. I would propose we use this bug to reinstate the original design.
Also note that when you first go into Panorama, if there's a group with a single tab, that tab fills the group at first, but then stops doing so when you start messing with it. That should be fixed as well (so it starts out half-width if need be).
Reporter | ||
Updated•14 years ago
|
Priority: -- → P4
Updated•13 years ago
|
Version: unspecified → Trunk
Assignee | ||
Comment 5•13 years ago
|
||
(In reply to Ian Gilman [:iangilman] from comment #1)
> I believe that the original design was that above a certain width, a lone
> tab would take only half the available width of the group. Otherwise you end
> up with a huge tab that fills the group entirely. By providing that extra
> space, we invite more tabs to be dropped in, and we avoid having the group
> just be an extra frame around the tab. Of course below a certain width, it
> made sense for the tab to fill the group, other wise it would be too small.
>
Not exactly. The original design is to make tabs flexible and fills the group space as much as possible. Whenever you drag a tab into a group, before you drop that tab, tabs inside the targeting group will automatically rearrange to make space for the new comer. I think this "half width tab" is just a kind mistake.
Assignee | ||
Comment 6•13 years ago
|
||
This root cause is that the group is reluctant to update column information when there is only one tab in the group. Thus, when a tab is removed from a two-columns-two-tabs group, the column number remains 2.
Comment 7•13 years ago
|
||
Comment on attachment 557397 [details] [diff] [review]
update column number even if there is only one tab in the group
Request a review
Attachment #557397 -
Flags: review?(tim.taubert)
Comment 9•13 years ago
|
||
Comment on attachment 557397 [details] [diff] [review]
update column number even if there is only one tab in the group
Review of attachment 557397 [details] [diff] [review]:
-----------------------------------------------------------------
Thanks, that looks good to me! Let's add a test for this. r- only for the missing test.
Attachment #557397 -
Flags: review?(tim.taubert) → review-
Assignee | ||
Comment 11•13 years ago
|
||
Thanks for advice from Tim.
Attachment #557397 -
Attachment is obsolete: true
Attachment #562951 -
Flags: review?
Assignee | ||
Updated•13 years ago
|
Attachment #562951 -
Flags: review? → review?(ttaubert)
Comment 12•13 years ago
|
||
Comment on attachment 562951 [details] [diff] [review]
patch with testcase
Review of attachment 562951 [details] [diff] [review]:
-----------------------------------------------------------------
Great, thanks! Can you please prepare the patch for checkin?
Here's some advice on how to do that: http://blog.bonardo.net/2010/06/22/so-youre-about-to-use-checkin-needed
Attachment #562951 -
Flags: review?(ttaubert) → review+
Updated•13 years ago
|
Assignee: nobody → marffin
Status: NEW → ASSIGNED
Assignee | ||
Comment 13•13 years ago
|
||
r=ttaubert
Attachment #562951 -
Attachment is obsolete: true
Attachment #563284 -
Flags: checkin?(ttaubert)
Assignee | ||
Updated•13 years ago
|
Keywords: checkin-needed
Updated•13 years ago
|
Whiteboard: [visual][polish][good first bug] → [visual][good first bug]
Target Milestone: Future → Firefox 10
Comment 14•13 years ago
|
||
Thanks for the patch!
https://hg.mozilla.org/integration/fx-team/rev/268ba6fecae0
Keywords: checkin-needed
Whiteboard: [visual][good first bug] → [visual][good first bug][fixed-in-fx-team]
Updated•13 years ago
|
Attachment #563284 -
Flags: checkin?(ttaubert) → checkin+
Comment 15•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Whiteboard: [visual][good first bug][fixed-in-fx-team] → [visual][good first bug]
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
•