From Bugzilla Helper: User-Agent: Mozilla/4.73 [en] (WinNT; U) BuildID: 2000070320 Tables using the fixed layout algorithm (table-layout:fixed) ignore the nowrap attribute (either set via CSS or as HTML attribute) Reproducible: Always Steps to Reproduce: 1. Create a table with one row and some cells 2. Set css widths for all cells 3. Ensure that at least one cell has overflowing content 4. Set either NOWRAP in the <TD> or white-space:nowrap as style 5. Load the table Actual Results: The overflowing content will be distributed to more than one line. Setting overflow:hidden for the overflowing cells does not help. Expected Results: The content should not be wrapped to more than one line. Instead, it should be clipped at the cells right side. Works fine with IE :( This bug may be related to #44505.
Bug occurs only when using nested tables. See testcase.
Independent of content lenght, the wrapping will never produce more than 2(!) lines.
Sorry, previous comment was an error. Wrapping _will_ produce more than 2 lines if necessary.
firstname.lastname@example.org could you split your testcase, to reflect only one problem per bugreport, the testcase is identical for bugs 44505-7. I splitted already one (overflow) but it would be much easier to handle the remaining unconfirmed bugs. Thanks Bernd
Bernd: Normally I would create one testcase per bug, but I'm currently writing my diploma thesis and have nearly "zarro" time left. I just thought that combined testcases are better than no testcases at all ?! Thank you for your understanding and for splitting them up.
I had difficulties to split the remainings bugs up, so thats why I am asked :-)
Confirming finally the bug, it was there for along time, but I did not have time to split the testcase. This bug looks related to 42832. Reducing summary text length
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Both white-space:nowrap and <TD NOWRAP> ignored when table-layout:fixed → NOWRAP ignored for fixed layout in a nested table
the testcase renders fine was fixed a time ago
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
QA contact update
QA Contact: chrisd → amar
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.