Open
Bug 448787
Opened 18 years ago
Updated 3 years ago
Table cell with "nowrap" does not take float width into account
Categories
(Core :: Layout: Tables, defect)
Core
Layout: Tables
Tracking
()
NEW
People
(Reporter: sam, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(1 file, 1 obsolete file)
|
921 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16
Build Identifier: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-3.1a2pre.en-US.win32.zip
If a table cell's colspan attribute is changed, if the table cell's white-space property is set to nowrap, if the table cell contains a floated element, if the table's width is constrained by a containing element and the table's table-layout property is automatic, the table cell's recalculated width does not account for the width of the floated element within the table cell.
Reproducible: Always
Steps to Reproduce:
1. go to url
2. see
3.
Actual Results:
the text of the table cell (th#a) overflows out of the cell.
Expected Results:
the cell grows to contain the text
originally found the bug on firefox 2.0.0.16 but I tested it on the latest build.
| Reporter | ||
Comment 1•18 years ago
|
||
| Reporter | ||
Comment 2•18 years ago
|
||
I am dumb and javascript / recalculation is unnecessary. The original calculation is wrong as well.
Attachment #331928 -
Attachment is obsolete: true
Comment 3•18 years ago
|
||
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.1a2pre) Gecko/2008080304 Minefield/3.1a2pre
I see the overlap too. Thanks for the clear testcase.
Related to bug 325412 and/or bug 83330?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: testcase
OS: Windows Vista → All
Hardware: PC → All
Summary: table cell width recalculated incorrectly → Table cell with "nowrap" does not take float width into account
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•