Closed
Bug 26787
Opened 25 years ago
Closed 24 years ago
bordercolor & bgcolour in tables not being rendered correctly
Categories
(Core :: Layout: Tables, defect, P3)
Tracking
()
VERIFIED
INVALID
People
(Reporter: tyger11, Assigned: karnaze)
References
()
Details
Check out the URL. 1) bordercolor in a TABLE tag is not fully working. It only does the left and top borders of the outer table border, and the bottom & right borders are being done in an alternating colour, to simulate depth or some such silliness. It should be a uniform colour. 2) the bordercolor in a TABLE tag is not being carried into the table cell border colors. Bad, bad, bad. 3) bgcolors in TR tags are not recognized, and/or are having problems when bgcolors are specified in TABLE, TR, _and_ TD tags. This behaviour should be looked into. All these problems are demonstrated on the sample URL.
Comment 1•25 years ago
|
||
Items 1 and 2 might have smth to do with bug 8381, item 3 seems a lot like bug 8524. Not sure whether these are dups or dependencies...
Changingto HTML Tables
Assignee: troy → karnaze
Component: Layout → HTMLTables
QA Contact: petersen → chrisd
Comment 3•25 years ago
|
||
Yep. Put a strict DTD in and it looks much better already.
Comment 4•24 years ago
|
||
Another site where this shows up is http://www.altavista.com
Assignee | ||
Comment 5•24 years ago
|
||
1) table borders are by default OUTSET. If you want solid borders change them through style rules. 2) I don't think bordercolor is inherited; at least Nav4.x doesn't seem to work this way. The CSS border-color is not inherited which gives support to this claim. The url looks similar to Nav4.x regarding border color. 3) insert <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> and you will get the effect you want. Marking INVALID.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Comment 7•24 years ago
|
||
Oops, ignore dup marking of bug 35581. I meant to mark that one a dup of bug 27687 instead.
Comment 9•24 years ago
|
||
karnaze makes a compelling case for INVALID, as well as a fix, so verifying.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•