208542 - table with collapsed solid borders not rendered properly when size gets large

Status: RESOLVED DUPLICATE of bug 244135

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

Description

[Ho KS]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529

The table is a repetition of chunks consisting of "header", "content" and
"seperator" cells. Table in the webpage consists of 20 chunks, pls see source
for indicator
The table appears fine if rendered in small number of chunks (tested OK up til 5)
More than that, the table will be missing borders, sometimes, partially rendered
borders (mouse droppings kind :P)

Found out that if I did a print preview, then close the preview, the table is
rendered properly.

Reproducible: Always

Steps to Reproduce:
To see problem with rendering
1. go to http://the.stormkeepers.org/testing.htm

To see problem go away temporarily
1. open print preview
2. close print preview
Actual Results:  
table not rendered properly, missing borders, lines

Expected Results:  
proper table with solid collapsed borders

Comment 1

[Ho KS]

Attachment: table with collapsed solid borders nested within another table

This renders correctly as opposed to when it's not nested within another table

Comment 2

[John Olsson]

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040914

I have also experience similiar behaviour in a large table. Somtetimes the table
is rendered correctly and sometimes it is not. Just changing a single character
in the HTML code of the table can trigger this (or cure the problem). Sometimes
the complete table lacks borders, sometimes only the upper portion.

But if I do a print preview, the preview is always correct and when the preview
is closed the table is rendered correctly. However by just pressing the reload
button nothing changes, but a shift click on the reload button (to force a
reload) will cause the problem to appear again.

This bug could be related to bug #244135.

Comment 3

[Aaron Lawrence]

The original poster's testcase site is gone, but I agree - I think this is a dupe of 244135. Marking as such.