Closed
Bug 246382
Opened 20 years ago
Closed 20 years ago
Left column is stretched far too wide on www.simtel.net
Categories
(Core :: Layout: Tables, defect, P1)
Tracking
()
RESOLVED
FIXED
mozilla1.8beta1
People
(Reporter: martijn.martijn, Assigned: dbaron)
References
()
Details
(Keywords: testcase)
Attachments
(1 file, 3 obsolete files)
676 bytes,
text/html; charset=UTF-8
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040601 Firefox/0.8.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040601 Firefox/0.8.0+ This seems like a regression of fixing bug 217527. The site looks good to me in: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/2004-05-31 Firefox/0.8.0+ and also good in: Firefox0.9 (1.7 build) 2004-06-08 But the site doesn't look good to me in: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040601 Firefox/0.8.0+ and also not good in: Firefox0.9 (1.7 build) 2004-06-11 This seems to correspond with the checkins of bug 217527. Reproducible: Always Steps to Reproduce: 1.Visit url 2. 3. Actual Results: Left column far too wide (like 1050px) Expected Results: Normal width for left column (more like 150px)
Assignee | ||
Comment 1•20 years ago
|
||
It was bug 217527 -- I backed that out of the 1.7 branch.
Assignee | ||
Updated•20 years ago
|
Assignee: nobody → dbaron
Flags: blocking1.8a2+
Priority: -- → P1
Target Milestone: --- → mozilla1.8alpha2
Assignee | ||
Comment 2•20 years ago
|
||
Assignee | ||
Comment 3•20 years ago
|
||
Attachment #150764 -
Attachment is obsolete: true
Assignee | ||
Comment 4•20 years ago
|
||
Attachment #150765 -
Attachment is obsolete: true
Assignee | ||
Comment 5•20 years ago
|
||
Comment on attachment 150766 [details]
simplified testcase
Expected results:
* the select should be narrow
Actual results:
* the select is the width of the page
Assignee | ||
Comment 6•20 years ago
|
||
Attachment #150766 -
Attachment is obsolete: true
Assignee | ||
Comment 7•20 years ago
|
||
I think the problem here is that combobox max-element-width calculation is fundamentally broken. (There's a little bit of code in Reflow that duplicates what's in ReflowCombobox, but the basic problem is ReflowCombobox setting the max-element-width to the width.)
Assignee | ||
Comment 8•20 years ago
|
||
Can anyone think of any cases where a combobox's max-element-width (min-intrinsic) and unconstrained width (intrinsic) should be different? I'm thinking there aren't any such cases.
We never wrap combobox OPTIONs, so no, there should be no difference.
Comment 10•20 years ago
|
||
nominating for aviary1.0 - would be good to fix this so that the fix that caused it can be applied to the branch.
Updated•20 years ago
|
Flags: blocking-aviary1.0?
Comment 11•20 years ago
|
||
Bug reproduced using: Mozilla 1.8a2 (Build ID: 2004070807) (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040708) Windows XP And Firefox 0.9 (1.7 Build) (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614)
Assignee | ||
Comment 12•20 years ago
|
||
I'll try to fix this for the next alpha.
Flags: blocking1.8a2+ → blocking1.8a2-
Updated•20 years ago
|
Flags: blocking-aviary1.0RC1+
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0+
Updated•20 years ago
|
Flags: blocking1.8a3?
Comment 13•20 years ago
|
||
is backing out the patch for http://bugzilla.mozilla.org/show_bug.cgi?id=217527 a good option for PR1 and 1.0 final?
Comment 14•20 years ago
|
||
chofmann: That was already done - the patch was backed out of the aviary and 1.7 branches shortly after it was put in, so this bug doesn't exist on the branches. I was guessing that this was marked as a blocker because without it, the other fix can't go into the branch. Would be nice not to ship 1.0 with the slashdot regression, but it's clearly better than having this bug...
Comment 15•20 years ago
|
||
ok, thanks. marking fixed aviary1.0 and I guess http://bugzilla.mozilla.org/show_bug.cgi?id=217527 should now get marked + so we can try to get the fix that solves both problems
Keywords: fixed-aviary1.0
Assignee | ||
Comment 16•20 years ago
|
||
See also the patch on bug 246999.
Target Milestone: mozilla1.8alpha2 → mozilla1.8beta
Updated•20 years ago
|
Flags: blocking1.8a3? → blocking1.8a3-
Comment 17•20 years ago
|
||
this isn't fixed on aviary - it was never a bug there. given that the other bug has been minused, removing blocking flags here along with the keyword.
Flags: blocking1.8a4?
Flags: blocking-aviary1.0PR+
Flags: blocking-aviary1.0+
Keywords: fixed-aviary1.0
Comment 18•20 years ago
|
||
*** Bug 256096 has been marked as a duplicate of this bug. ***
Comment 19•20 years ago
|
||
The url works now with the fix for bug 246999, but the testcase is still wrong.
Comment 20•20 years ago
|
||
the patch in bug 226637 fixes the remaining problem in the testcase
Depends on: 226637
Updated•20 years ago
|
Flags: blocking-aviary1.0?
Updated•20 years ago
|
Flags: blocking-aviary1.0?
Updated•20 years ago
|
Flags: blocking1.8a4?
Flags: blocking1.8a4-
Flags: blocking1.8a3-
Flags: blocking1.8a2-
Comment 21•20 years ago
|
||
the remaining issue with testcase is now fixed by the patch in bug 226637
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•