Closed
Bug 6304
Opened 25 years ago
Closed 25 years ago
"Overlapped" rowspans do not correctly calculate cellspacing
Categories
(Core :: Layout: Tables, defect, P3)
Tracking
()
VERIFIED
FIXED
M10
People
(Reporter: 3jrgm, Assigned: karnaze)
References
Details
(Whiteboard: [TESTCASE] need to consider case where 'pseudo' cols are 'created')
Attachments
(1 file)
(deleted),
text/html
|
Details |
The test case (to follow) describes a situation where there are "overlapping"
rowspan cells but no "real" rows to support the positioning. However, it's
probably easier to look at the attachment than to explain it in words (but
there are further comments in the attachment).
I also did the column-wise analogue for this testcase, and wound up with
another example of bug #1302 "minor table snafu on this page -- over-specified
colspans". (posted the analogue test case at bug #1302)
Reporter | ||
Comment 1•25 years ago
|
||
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M8
Reporter | ||
Updated•25 years ago
|
Whiteboard: [TESTCASE] need to consider case where 'pseudo' cols are 'created'
Assignee | ||
Comment 2•25 years ago
|
||
Moving to M9.
Assignee | ||
Updated•25 years ago
|
Target Milestone: M9 → M10
Assignee | ||
Comment 3•25 years ago
|
||
Moving to M10
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•25 years ago
|
||
Fixed with 8/19 changes.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 5•25 years ago
|
||
Using 9/16 Apprunner, verified fixed.
URL: test case attached
You need to log in
before you can comment on or make changes to this bug.
Description
•