Closed Bug 6304 Opened 25 years ago Closed 25 years ago

"Overlapped" rowspans do not correctly calculate cellspacing

Categories

(Core :: Layout: Tables, defect, P3)

Product:
Core
Component:
Layout: Tables
Platform:
x86
Windows 95
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: 3jrgm, Assigned: karnaze)

References

Details

(Whiteboard: [TESTCASE] need to consider case where 'pseudo' cols are 'created')

Attachments

(1 file)

testcase; overlapping rowspanning cells and cellspacing
3.14 KB, 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)
Status: NEW → ASSIGNED
Target Milestone: M8
Whiteboard: [TESTCASE] need to consider case where 'pseudo' cols are 'created'
Blocks: 7714
Moving to M9.
Target Milestone: M9 → M10
Moving to M10
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fixed with 8/19 changes.
Status: RESOLVED → VERIFIED
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.

Attachment

General

Creator:
Created:
Updated:
Size: