Closed
Bug 589304
Opened 14 years ago
Closed 14 years ago
When tabs are small enough to hide the close icon, stack tabs
Categories
(Firefox Graveyard :: Panorama, defect, P2)
Firefox Graveyard
Panorama
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: tchung, Assigned: iangilman)
References
Details
(Keywords: ux-userfeedback)
Attachments
(2 files, 1 obsolete file)
17.60 KB,
image/png
|
Details | |
1.61 KB,
patch
|
Dolske
:
review+
aza
:
feedback+
beltzner
:
approval2.0+
|
Details | Diff | Splinter Review |
The Close option (X), goes away when resizing a tab thumbnail in tabcandy view. We should either limit the size a tab can be resized to minimum, or keep the Close option always visible.
See screenshot
Repro:
1) install Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b5pre) Gecko/20100819 Minefield/4.0b5pre
2) open tabcandy and create a few tabs there
3) hold the bottom right corner of a tab and resize it small
4) Verify the tab thumbnail loses the close (X) after a certain size
Expected:
- keep the close X button around or limit the size of reduction
Actual:
- close X button goes away
Comment 1•14 years ago
|
||
Perhaps in cases when the thumbnail is too small to show it neatly, we can hide it, but then display it again (fade it back in) when we hover over the tab?
Assignee | ||
Comment 2•14 years ago
|
||
Below a certain size, thumbnails are so small that the close box would take up almost the entire space, making it difficult to interact with the thumbnail without accidentally closing it. At that size, move and resize are more important than close.
Perhaps that threshold could be a little lower (allowing thumbnails the size shown in the screen shot to still have close boxes), but we need that cut-off at some point.
Another possibility is we can tweak the "stack" threshold so that by the time thumbnails are too small for a close box, they stack instead.
Assignee: nobody → aza
Comment 3•14 years ago
|
||
(In reply to comment #2)
> Another possibility is we can tweak the "stack" threshold so that by the time
> thumbnails are too small for a close box, they stack instead.
LIKE.
Priority: P4 → P3
Comment 4•14 years ago
|
||
I concur, the solution should be:
> To tweak the "stack" threshold so that by the time thumbnails are
> too small for a close box, they stack instead.
We should also:
* Decrease the size at which the close icon closes.
Priority: P3 → P2
Summary: Tab thumbnail loses close option when resized to a minimal view → When tabs are small enough to hide the close icon, stack tabs
Assignee | ||
Comment 5•14 years ago
|
||
What about orphan tabs? What happens when they get too small?
Comment 6•14 years ago
|
||
I don't think orphan tabs are any different; we are removing the close icons so that you don't accidentally close a tab as the clickable area for zooming in is going to zero.
Comment 7•14 years ago
|
||
* Decreased the size at which tabs lose their close button
* Tweaked the size at which stacks form (although in the end decided to have a state where tabs don't have close buttons using my wishy-washy "felt right" metric)
Attachment #477136 -
Flags: feedback?(ian)
Assignee | ||
Comment 8•14 years ago
|
||
Comment on attachment 477136 [details] [diff] [review]
Patch v1
shouldStack: function GroupItem_shouldStack(count) {
if (count <= 1)
return false;
-
+
Replacing an empty blank line with one that has spaces in it is frowned upon.
Otherwise looks good. I don't think this kind of change needs a test.
Attachment #477136 -
Flags: feedback?(ian) → feedback+
Comment 9•14 years ago
|
||
Fixed Ian's nit.
Attachment #477136 -
Attachment is obsolete: true
Attachment #477171 -
Flags: review?(dietrich)
Attachment #477171 -
Flags: feedback+
Assignee | ||
Comment 10•14 years ago
|
||
Comment on attachment 477171 [details] [diff] [review]
Patch v1.1
Reassigning review to dolske while dietrich is jammed up with b7 stuff.
Attachment #477171 -
Flags: review?(dietrich) → review?(dolske)
Updated•14 years ago
|
Status: NEW → ASSIGNED
Updated•14 years ago
|
Assignee: aza → ian
Comment 11•14 years ago
|
||
Comment on attachment 477171 [details] [diff] [review]
Patch v1.1
>- return (rects[0].width < TabItems.minTabWidth * 1.35);
>+ return (rects[0].width < 55);
Sorta feels like this should be a constant defined somewhere, but I guess it's fine.
Attachment #477171 -
Flags: review?(dolske) → review+
Assignee | ||
Updated•14 years ago
|
Attachment #477171 -
Flags: approval2.0?
Comment 12•14 years ago
|
||
Comment on attachment 477171 [details] [diff] [review]
Patch v1.1
a=beltzner
Attachment #477171 -
Flags: approval2.0? → approval2.0+
Assignee | ||
Comment 13•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 14•14 years ago
|
||
verified with 20101013 build of minefield
However there is a bit of shrinking allowed between close button disappearance and stacking. Is that the wishy-washiness mentioned in comment 7?
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 15•14 years ago
|
||
(In reply to comment #14)
> verified with 20101013 build of minefield
>
> However there is a bit of shrinking allowed between close button disappearance
> and stacking. Is that the wishy-washiness mentioned in comment 7?
Indeed it is.
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
•