Closed Bug 107669 Opened 23 years ago Closed 23 years ago

tab buttons do not resize themselves correctly [with large screen size]

Categories

(SeaMonkey :: Tabbed Browser, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.9

People

(Reporter: phil_mozilla, Assigned: jag+mozilla)

References

Details

(Keywords: polish)

Attachments

(11 files)

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0; COM+ 1.0.2204)
BuildID:    2001102903

when there are 5 or fewer active tabs, the size of the tab buttons appears to 
be wrong.  As long as there are 6 or more tabs open, the tab buttons are sized 
so that the total area they take up is about 90% of the tab bar, leaving some 
room to the right.  This appears to be the correct behavior.

However, as long as the number of tabs is less than 5, the total area consumed 
by the tab buttons is about 1/8'th of the total area of the tab bar, with the 
very narrow tab buttons bunched a tthe extreme left of the bar.

Reproducible: Always
Steps to Reproduce:
1.Launch mozilla.
2.Observe that the initial tab button is very small ( only about 3 
characters of the site title are displayed )
3. hit CTRL+T to open tabs 2, 3, 4 and 5. 
4. Observe that the subsequent tab buttons are also very small, and all the 
tabs are bunched at the left edge of the screen
5. hit CRTL+T again to open tab #6.
6. note that the tab buttons now resize themselves correctly.

Actual Results:  Tab buttons were displayed incorrectly as long as the number 
of active tabs was 5 or less.

Expected Results:  Initial tab(s) should size themselves proportionally, to 
consume a constant part of the tab bar, up to some maximum size per tab button.

Windows NT server 4.0, x86.  Using 1600x1024 screen resolution.
ignore the user-agent listed in the description above. I had to submit this bug 
using IE, due to a different problem.  I then forgot to take the IE user-agent 
string out of the description.
works correctly for me, win2k current trunk.
I suspect this is just fastload file badness.  Delete your XUL.mfl file from
your profile dir.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Deleted XUL.mfl from the profile directory, still seeing same behavior.

Additionally, I have noticed that this behavior is affected by the size of the
mozilla window.   When I resize mozilla to about 1/2 of my total screen width, I
get proper tab sizing, even with only one or two tabs open.

Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Have also found that the tabs behave correctly, in this regard, when I lower my
screen resolution to 1024 x 768.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Very odd. I boosted my display up to 1600x1200 (from 1280x1024), and I can 
reproduce this in win2k. Most likely some window and/or box bug in calculating 
available space.
Um, so I was showing this to hyatt, except, well, I can't make this happen 
anymore. Phillip, is this still happening in a build from today? [Very weird].
John, I'm still getting the exact same behavior, using build 2001103103. 
*** Bug 108301 has been marked as a duplicate of this bug. ***
*** Bug 109248 has been marked as a duplicate of this bug. ***
I'm seeing this on both Linux and Windows, build 2001110121
*** Bug 111275 has been marked as a duplicate of this bug. ***
Summary: tab buttons do not resize themselves correctly. → tab buttons do not resize themselves correctly [with large screen size]
*** Bug 111433 has been marked as a duplicate of this bug. ***
*** Bug 111592 has been marked as a duplicate of this bug. ***
*** Bug 111618 has been marked as a duplicate of this bug. ***
I tested this on Linux build 2001111909 to get some numbers on what is "large
screen size". Results:

1195 pixels width - Tabs appear normally
1196 pixels width - Tabs become really tiny

This works in both ways (i.e. it switches "mode" regardless if I'm going from
larger to smaller size or the other way around)
While the presence of a sidebar definitely affects whether the tab
labels are displayed correctly, it has to be sufficiently wide. I
suspect this is actually a by product of just ensuring that the
visible display area is sufficiently narrow to not trigger the bug.
See the attached screenshot.

FWIW, without a sidebar, a 1213 pixel wide window works fine for me,
while a 1214 pixel wide window doesn't. This is on both 1600x1200
and 1920x1440 displays under Linux.
Having just checked, it seems my 1213/1214 pixel wide display corresponds
to an 1199/1200 pixel wide main HTML pane in Mozilla.
A tab size is calculated by layouter
(layout/xul/base/src/nsSprocketLayout.cpp?)
But I think tabbox flex was too big for it. (Why they use 100000?)
*** Bug 112219 has been marked as a duplicate of this bug. ***
*** Bug 112256 has been marked as a duplicate of this bug. ***
OS: Windows NT → All
QA Contact: blakeross → sairuh
Target Milestone: --- → mozilla1.1
*** Bug 113113 has been marked as a duplicate of this bug. ***
I can confirm that the proposed patch works.

Steve
*** Bug 113619 has been marked as a duplicate of this bug. ***
10 dups menas this should be marked mostfreq, right?
*** Bug 113786 has been marked as a duplicate of this bug. ***
*** Bug 114335 has been marked as a duplicate of this bug. ***
*** Bug 114610 has been marked as a duplicate of this bug. ***
*** Bug 114884 has been marked as a duplicate of this bug. ***
-> Added keywords

15 dups, and the patch is only a 2 line change ... perhaps somebody can review
this, and check it in !?!
Keywords: patch, polish, review
Comment on attachment 59299 [details] [diff] [review]
adhoc flex size patch (test with mozilla-0.9.6)

It looks safe to me. 
I bet it was a hack/workaround for something else though (why would anyone
otherwise set flex to such a big value?)

Have you tested this thorougly too?

r=hwaara... hyatt: sr=?
Attachment #59299 - Flags: review+
I cannot find any problems with a flex value of 1.

The change from flex 1 to 10000 has been made between revisions 1.8 and 1.9 (Oct
25):
http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=tabbrowser.xml&root=/cvsroot&subdir=mozilla/xpfe/global/resources/content/bindings&command=DIFF_FRAMESET&rev1=1.8&rev2=1.9

Comment for the checkin is:
Fix for bug 105587, tabs should support autohide, also other tabbrowser fixes. 

Not very helpful, since this is probably one of the "other fixes" ... Perhaps
hyatt still knows what this was for.
*** Bug 116517 has been marked as a duplicate of this bug. ***
*** Bug 116812 has been marked as a duplicate of this bug. ***
*** Bug 116893 has been marked as a duplicate of this bug. ***
*** Bug 118693 has been marked as a duplicate of this bug. ***
Reassigning to new component owner.
Assignee: hyatt → jaggernaut
Status: ASSIGNED → NEW
This worksforme on win2k with a 1600x1280 screen (current trunk build).

Can anyone esle still reproduce this?
It still does it, on W2K 1600x1200, maximized, build ID: 2002012103
Could someone go to comment 24 of bug 113798 to check if the patch fix this bug ?

*** Bug 122155 has been marked as a duplicate of this bug. ***
*** Bug 122020 has been marked as a duplicate of this bug. ***
*** Bug 122220 has been marked as a duplicate of this bug. ***
*** Bug 122948 has been marked as a duplicate of this bug. ***
*** Bug 123507 has been marked as a duplicate of this bug. ***
*** Bug 123657 has been marked as a duplicate of this bug. ***
*** Bug 123720 has been marked as a duplicate of this bug. ***
The reason 100000 was chosen is because the flex needs to be so much greater 
than the flex on the spacer that the spacer won't compress the tabs 
unnecessarily. See the next two attachments to see what I mean.
Attached image flex="1"
Attached image flex="100"
Attached patch Use flex="100"Splinter Review
A flex of 100 keeps the spacer from compressing unnecessarily, and from what I
understand it avoids the bug some people are seeing with the tabs being too
small when there are only a small number of them.
*** Bug 122791 has been marked as a duplicate of this bug. ***
Comment on attachment 68101 [details] [diff] [review]
Use flex="100"

r=bryner
Attachment #68101 - Flags: review+
-> 0.9.9
Target Milestone: mozilla1.1 → mozilla0.9.9
*** Bug 124876 has been marked as a duplicate of this bug. ***
Smaug: I checked in your 100000 -> 100 fix. Thanks for the idea.
Status: NEW → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
*** Bug 126132 has been marked as a duplicate of this bug. ***
*** Bug 126680 has been marked as a duplicate of this bug. ***
*** Bug 127328 has been marked as a duplicate of this bug. ***
*** Bug 130029 has been marked as a duplicate of this bug. ***
*** Bug 130032 has been marked as a duplicate of this bug. ***
appears to be working fine, using 2002.03.13.09 comm bits on win2k, with
resolution set to 1600x1200.
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: