Closed Bug 134261 Opened 18 years ago Closed 18 years ago

Background color not rendered on COL or COLGROUP elements

Categories

(Core :: Layout: Tables, defect, P2, major)

defect

Tracking

()

VERIFIED DUPLICATE of bug 4510

People

(Reporter: chrispetersen, Assigned: karnaze)

References

()

Details

(Keywords: regression, topembed)

Attachments

(1 file)

Keywords: regression, xhtml
This regression occured on the Feb 21 builds (2002-02-21-03). The previous build
(2002-02-20-16) rendered the page with assigned lime background color.
Adding topembed. Occurs on the mfcembed March 27 0.9.9 build.
Severity: normal → major
Keywords: topembed
Priority: -- → P2
The most likely candidate seems to be bernd.mielke@snafu.de checkin to bug 4510.
Actually the patch was made by fantasai.

As you can see from the attached testcase this is not XHTML specific; HTML
regressed as well. Reassigning to HTML Tables.

Nominating for nsbeta1.
Assignee: heikki → karnaze
Component: XML → HTMLTables
Keywords: xhtmlnsbeta1
QA Contact: petersen → amar
its a dupe of 4510

*** This bug has been marked as a duplicate of 4510 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
How can this be dupe if this appeared when the patch in bug 4510 was checked in?
very easily, if the remaining issue in bug 4510 is column background
I think this regression affects xhtml documents and html documents rendered in
standards mode. I couldn't get the background color to appear in quirks mode.
My point is this was working with the test cases provided.
Then, the regression occured in the Feb 21 build.
Heikki -- The patch checked in for 4510 was a temporary fix; the bug's still 
open for having CSS2 compliant background rendering in Standard mode. (The patch 
reverted Standard mode to using Quirks rendering.)

The reason we took out the Standard mode rendering is because it was incorrect 
per CSS2, and if we're going to be incorrect, we might as well be consistent 
with MSIE and other incorrect browsers.
 Verified dupe of Bug # 4510
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.