Closed
Bug 22774
Opened 25 years ago
Closed 24 years ago
[FLOAT] flow around tables seems to retain state inappropriatly
Categories
(Core :: Layout: Tables, defect, P2)
Tracking
()
People
(Reporter: ben, Assigned: buster)
References
()
Details
(Keywords: testcase, Whiteboard: [TESTCASE])
Attachments
(1 file)
|
(deleted),
text/html
|
Details |
The flow around the tables doesn't seem to work right. I have main text with two
tables off to the side and the text doesn't return to full width after flowing
around the tables.
|
||
Comment 1•25 years ago
|
||
|
|
||
Updated•25 years ago
|
Whiteboard: [TESTCASE]
|
|
||
Comment 2•25 years ago
|
||
Seems like <OL> (and <UL>) doesn't use the available space after a right
floating table. At the original URL there is also a typo that makes the rest
of the page be part of an <ol> (the <ol> is matched with </ul>).
|
||
Updated•25 years ago
|
Assignee: karnaze → kipp
|
|
||
Comment 3•25 years ago
|
||
The block code is at fault. Reassigning to Kipp.
Summary: flow around tables seems to retain state inappropriatly → [FLOAT] flow around tables seems to retain state inappropriatly
|
||
Comment 4•25 years ago
|
||
Bulk moving [testcase] code to new testcase keyword. Sorry for the spam!
Keywords: testcase
mine! mine mine mine! all mine! whoo-hoo!
Assignee: kipp → buster
I see 2 problems. The one originally reported, and the "introduction" getting
placed in the left edge of the page near the top of the document.
redistributing bugs across future milestones, sorry for the spam
Target Milestone: M18 → M19
|
||
Comment 9•24 years ago
|
||
I think bug 35666 explains why we are doing this -- perhaps this should be
marked a duplicate, although this is really kind-of invalid since the HTML is so
messed up (using </ul> instead of </ol> means neither the LI or UL is ever closed).
|
||
Comment 10•24 years ago
|
||
*** This bug has been marked as a duplicate of 35666 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
|
||
Comment 12•22 years ago
|
||
*** Bug 156244 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•