Closed
Bug 207675
Opened 21 years ago
Closed 21 years ago
Text not wrapped
Categories
(Core :: Layout: Tables, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 201001
People
(Reporter: steven, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
751 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 The text beginning with "Congestion charging is a way of ensuring..." is not correctly wrapped in Mozilla, but it is in IE6. Reproducible: Always Steps to Reproduce: 1. Navigate to URL with Mozilla 2. Look at screen 3. Become confused when the first sentence doesn't make sense Actual Results: Therapy. Lots of Therapy. Expected Results: Wrapped the text as IE does. Thanks for writing such a cool browser, it has supplanted IE as my daily browser on Windows... and Linux.
Comment 1•21 years ago
|
||
Confirming. Odd, because when you select it, the highlighting is weird, and if you copy paste, you get all the text.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•21 years ago
|
||
Comment 3•21 years ago
|
||
I have no idea if that's the expected behaviour.
Comment 4•21 years ago
|
||
Nice testcase. Additionally I noticed that adding a width to the inner abs. pos. DIV makes the text wrap (even "width:0px" will do). Also, the left position is dynamically changed with JavaScript and the layout of the URL is correct for that part. Changing the TABLE to a DIV makes the text wrap, so it seems to be a table problem when inside a nested abs. pos. block without a specified width.
Assignee: general → table
Severity: normal → minor
Component: Browser-General → Layout: Tables
Keywords: testcase
OS: Windows XP → All
QA Contact: general → madhur
Comment 5•21 years ago
|
||
*** Bug 207723 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 201001 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•