Closed Bug 33612 Opened 26 years ago Closed 25 years ago

table cell produces extraneous border pixels

Categories

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

x86
Windows 95
defect

Tracking

()

VERIFIED INVALID
Future

People

(Reporter: decoy, Assigned: karnaze)

References

()

Details

Build: 2000032308 In the example, the wide, spanned cell at the bottom of the two row table has some extra pixels in its left hand border. They seem reproducible regardless of resolution. This smells like a fencepost error in the table rendering routines. HTML: <table class="recordset"> <col class="col1"/><col class="col2"/> <tr><th class="time">12Mar2000</th> <th><a href="items/00000100">Algerian forces advance</a> [<a href="mirror/00000100">Mirrored</a>] [<a href="reflect/00000100">Original</a>]</th></tr> <tr><td colspan="2" class="content">Explanation and introduction here</td></tr> </table> CSS: table.recordset {border-collapse:collapse; width:100%;} table.recordset th {text-align:left; font-variant:small-caps; border:1px outset #405080; background-color:#405080;} table.recordset th a {font-style:normal;} table.recordset th.time {text-align:left; font-style:oblique; font-variant:normal; border:1px outset #405090; background-color:#405090;} table.recordset td {padding:1px;} table.recordset td.content {border:1px outset #405080;} table.recordset col.col1 {width:10%;} table.recordset col.col2 {width:90%;}
Changing component to tables
Assignee: troy → karnaze
Component: Layout → HTMLTables
QA Contact: petersen → chrisd
decoy@iki.fi - this looks OK to me. Are you still seeing this problem with recent builds of Mozilla? Gerv
The page referenced in the URL currentally will not render. bug 38228
Refer to 18941, 19956, 29125, 34520 and 38228. The <xml> declaration prevents rendering, and the strict doctype causes some table layout problems. I'd suggest marking this as a duplicate.
setting as new. feel free to dupe it. none of those bugs look like an exact duplicate to me.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug, or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Is this bug caused by border-collapse? If yes it is dependant on bug 41262.
After really delving into the CSS2 spec, and the bugs surrounding the collapsed border model, I now feel the best way to deal with this one is to INVALIDATE and RESOLVE it. I think what I've reported is some combination of early border- collapse bugs and my previous ignorance of border conflict resolution. I will revitalize this one if the problem persists after the rewrite of the collapsed borders code.
Went over the output with a microscope - the extraneous pixels were a cell border, rendered precisely as they should be. The coloring, and Mozilla's choice of a rendering different from IE's for border-style:outset, confused me. Marking invalid, with a sorry to those bothered.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
QA contact update
QA Contact: chrisd → amar
This is a border collapse bug.. From the above comments this is invalid and we no longer support win95
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.