[PP]COLGROUP attribute/value 'width=rel' not working properly.

VERIFIED FIXED in M9

Status

()

Core
Layout: Tables
P3
normal
VERIFIED FIXED
19 years ago
19 years ago

People

(Reporter: Christine Hoffman, Assigned: karnaze (gone))

Tracking

Trunk
x86
Windows 95
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

19 years ago
Using 5/13 Apprunner on Win 95,Win NT, Win 98, Linux(5/13 Viewer), and
Mac8.5(5/12 Apprunner).

Open the URL. There are two tables with widths assigned to colgroups. The first
table uses pixels and relative widths. The second table uses pixels.

Expected results: The table should display the same.
Actual results: The table with the pixels and relative widths does not display
correctly. The browser should allot the pixel length, then divide the
remaining space with the relative lengths. In this case 3* should be alloted
three times the remaining space and 1* should be alloted 1 times the remaining
space -- in other words -- 200, 300, 100.

Behavior on Mac is OK. Win 95, Win NT, Win 98 and Linux have the bug.
(Reporter)

Comment 1

19 years ago
Created attachment 174 [details]
HTML file
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: M9

Comment 2

19 years ago
This may be related to bug#5797 , as it also deals with problems calculating
table widths.

Comment 3

19 years ago
This has nothing to do with 'width=rel'. The real bug is that
when both <table> and <colgroup> specifies 'width' the cells
gets wrong width (even when using absolute widths).
see bug#9156
(Reporter)

Comment 4

19 years ago
Chris: mats@symsoft.se in his 7/1 comments says this is not a width=rel problem.
However, it now seems to be fixed. See if you agree - if you do, please mark it
fixed. Bug #3967 looks to be the same problem and that bug is marked fixed.
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 5

19 years ago
Fixed with 7/28 changes.
(Reporter)

Updated

19 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Comment 6

19 years ago
Verified bug fixed.
You need to log in before you can comment on or make changes to this bug.