Closed
Bug 22122
Opened 25 years ago
Closed 25 years ago
COLGROUP width=0* - wrong implementation
Categories
(Core :: Layout: Tables, defect, P3)
Tracking
()
VERIFIED
FIXED
M14
People
(Reporter: fantasai.bugs, Assigned: karnaze)
Details
Attachments
(1 file)
(deleted),
text/html
|
Details |
Overview Description:
Setting the width of a column to 0* makes the column excessively wide,
overriding even explicit table widths.
Steps to Reproduce:
I'm going to attach a test case.
Actual results:
Table 1: 3rd col - minimum width
(correct) 2nd col - 1/2 remaining width
1st col - 1/2 remaining width
Table 2.1: 3rd col - width far exceeding screen width
2nd col - minimum width
1st col - width equal to 2nd col (correct)
Table 2.2: 3rd col - width far exceeding screen
2nd col - minimum width
1st col - twice the width of 2nd col (correct)
Table 2.3: 3rd col - width far exceeding screen
2nd col - 100 pixels (correct)
1st col - minimum width
Comments on actual test case results:
Table 1 came out correctly.
Table 2.1: First two columns allotted minimum width--
last column seems to extend more than 30x table width
Table 2.2: Relative widths are still implemented,
even though 1* has been minimized.
Table 2.3: Pixel width correctly implemented,
even when combined with 0*
Expected Width allotment:
Table 1: As is
Table 2.1: 3rd col - minimum width
2nd col - 1/2 of remaining space
1st col - 1/2 of remaining space
Table 2.2: 3rd col - minimum width
2nd col - 1/3 of remaining space
1st col - 2/3 of remaining space
Table 2.3: 3rd col - minimum width
2nd col - 100 pixels
1st col - remaining space
Build Date & Platform Bug Found:
Latest under December 18, 1999 on Windows NT 4
Additional Information:
HTML Spec: http://www.w3.org/TR/REC-html40/struct/tables.html#h-11.2.4.4
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14
Assignee | ||
Comment 2•25 years ago
|
||
Fixed with latest checkin.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•