367576 - [BC] multiple consecutive rowspan cells in second column have a line from first column when rules="rows" or adjacent td have border-top/border-bottom when border-collapse:collapse

Status: RESOLVED DUPLICATE of bug 332740

(Core :: Layout: Tables, defect)

Description

[Mardeg]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

The line that appears inside the spanning cell in the second column is always a continuation of the first spanned cell line of the first column, regardless of how many cells are spanned.
The line only appears in consecutive rowspanning cells that are NOT the first or last spanning cell in the second column. The last cell does not need to be a rowspan for the lines to appear in the above rowspanning cells.
The line appears in both strict and quirks mode.
I haven't tested for the bug in a table with three or more columns.
The bug disappears when rules="all" is used.
This still needs to be tested on nightly builds and other OSes.
Non-gecko browsers do not show this bug.


Reproducible: Always

Steps to Reproduce:
1. Visit the URL link for a minimal test case.

Actual Results:  
Lines from the first column of cells carry through to rowspanning cells in the second column

Expected Results:  
Rowspanning cells in the second column should not have lines through them.

I'll attach a screenshot of the display I see.

Comment 1

[Mardeg]

Attachment: screenshot of lines through second column rowspans

Comment 2

[Colin Barrett [:cbarrett]]

I'm seeing this on Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

Comment 4

[Mardeg]

Attachment: Testcase with colspan

Adding extra columns shows the buggy line does not follow through beyond the column immediately adjacent, even if it's into a multi-column spanned cell.

Comment 5

[Mardeg]

Another method found to show this bug was filed, bug 391417 with https://bugzilla.mozilla.org/attachment.cgi?id=275820
Re-opening as this seems independant of bug 332740

Comment 7

[Colin Barrett [:cbarrett]]

Confirmed in Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9a9pre) Gecko/2007103104 Minefield/3.0a9pre

Comment 8

[Mardeg]

Increased severity to Major as 3rd table in testcase at https://bugzilla.mozilla.org/attachment.cgi?id=288066 shows it can obscure text completely. requesting blocking1.9

Comment 9

[Mardeg]

Attachment: testcase showing obscured text

Comment 10

[Mike Schroepfer]

Minusing for 1.9 blockign since this also occurs in 1.8.1 per comment 2.  If this is incorrect or you disagree please renominate

Comment 11

[Boris Zbarsky [:bzbarsky]]

This should probably depend on the rules/border rewrite bug...

Comment 12

[Mardeg]

Attachment: Screenshot of buggy borders being cleared by passing another app over them

when dragging another app window over firefox, I was able to wholly and partially clear the buggy borders, and also have them wholly and partially re-appear if the other app ran over the point where the buggy part of the lines started.

Comment 13

[Mardeg]

from Fantasia (bug 43178): "Certain values of the 'rules' attribute trigger border-collapse:
we can't put borders on rows and columns in the separated borders
model."

Comment 14

[Bernd]

the problem is solely a colspan issue + border collapse

Comment 15

[Timwi]

I think this is a duplicate of Bug 332740?

Comment 16

[Mardeg]

(In reply to Timwi from comment #15)
> I think this is a duplicate of Bug 332740?

Agreed, duping based on comments 13 and 14