Bug 183635 - Borders disappear in large tables
Summary: Borders disappear in large tables
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: mozilla
Version: 4.0
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
: ---
Assignee: Christopher Aillon
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks: 234251
TreeView+ depends on / blocked
 
Reported: 2006-03-02 13:40 UTC by Göran Uddeborg
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-07-31 20:04:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
HTML file triggering the problem (19.52 KB, text/html)
2006-03-02 13:40 UTC, Göran Uddeborg
no flags Details

Description Göran Uddeborg 2006-03-02 13:40:06 UTC
Created attachment 125531 [details]
HTML file triggering the problem

Comment 1 Göran Uddeborg 2006-03-02 13:40:06 UTC
Description of problem:
When displaying large tables, the borders between the cells disappear.  Not all
borders in the table disappear, only some, and the pattern is apparently random.
 I attach a sample HTML file which triggers the problem for us.

Version-Release number of selected component (if applicable):
mozilla-1.7.12-1.4.2
firefox-1.0.7-1.4.3

How reproducible:
Most of the time, but not always.  I can't see any real pattern.  Also, if I
just page up and down in the table, the details may vary.  Borders that were
there at first may disappear when I get back to the same place later, and vice
versa.

Steps to Reproduce:
1. mozilla .../o.html
where o.html is the attached file.
  
Actual results:
Some borders in the table missing.

Expected results:
All borders there.

Additional info:
The size of o.html appears to be close to some limit.  If I remove one or two
rows, I see all borders most, if not all, of the time.

Comment 9 RHEL Program Management 2007-07-31 20:04:49 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request. 


Note You need to log in before you can comment on or make changes to this bug.