Closed Bug 91526 Opened 23 years ago Closed 23 years ago

people.yahoo.com is far too wide

Categories

(Core :: Layout: Tables, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: alexsavulov)

References

()

Details

(Keywords: testcase, top100, Whiteboard: vtrunk)

Attachments

(1 file, 1 obsolete file)

Today's comm. branch build

people.yahoo.com is way too wide; looks like a table issue.
Attached file Testcase (obsolete) —
Problem seems to be caused by a NOWRAP attribute.
Keywords: testcase
Keywords: top100
I think karnaze is out of the office.  Can anyone say what's the right thing to
do here?  Is this really an evangelism bug?  Is this really a feature of NOWRAP?
It is not a feature or NOWRAP. There is a bug here, probably specific to
processing of the NOWRAP attribute.
When did this bug start?

There's no spec for this type of thing, so it's hard to say if it's a bug with
the page.  What's happening is that they specify a table with 4 cells (the
upper-right one is not in the document and implied, and the lower two are
joined) where the upper left cell should have a width of 1% of the entire table.
 However, IE (and this is consistent with what CSS says about percentage widths)
ignores this percentage width, presumably since the parent has no fixed with and
the width attribute on TD acts more like a min-width.  Then we expand the parent
based on the child, which seems wrong.  Maybe it's happening because we end up
with four reflow passes due to the nested tables?

Karnaze should be around.  He was yesterday, at least.
I will try to simplify this. 
reassigning to me since it seems to be realted to 80817
Assignee: karnaze → alexsavulov
If you change all the width="1%" to width="0" the page will display much better
although still not exactly like IE.
Will add my testcase demonstrating the problem with width="1%". Agreed that the
NOWRAP is also another workaround to the problem. 
second test case (attachment 44169 [details]) gets handled like IE does - where is the
problem here?
Depends on: 93363
fixed on trunk
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Whiteboard: vtrunk
Alexandru Savulov, second testcase attached works fine but the first test case 
attached by Mats Palmgren does not work and IE handles it differently. The 
NOWRAP seems to be a problem here. I am reopening this bug and if you think that 
the original problem described in this bug was fixed, you can close this bug
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Other issues should be filed as a separate bug.  Please describe actual vs.
expected results more clearly.  "IE handles it differently" doesn't help those
people who don't have IE and it doesn't say which version of IE you're talking
about.
Comment on attachment 43334 [details]
Testcase

opened bug 120191 for this testcase since it didn't displayed the problem of
the URL
Attachment #43334 - Attachment is obsolete: true
closing the bug FIXED since URL works

opened bug 120191 for the first (obsoleted) testcase

Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
 A new bug was opened for the first testcase failure. The second testcase works
fine. I am closing this bug. Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: