Closed Bug 74208 Opened 24 years ago Closed 24 years ago

Mozilla fails to render the page properly after the DOM has been updated.

Categories

(Core Graveyard :: GFX, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: skhan, Assigned: kmcclusk)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; 0.8.1) Gecko/20010323 BuildID: 2001032319 I have javascript code that toggles the visibility of table rows. When rows are made visible, Mozilla doesn't always update the whole page to reflect the additional rows. As such, things get overwritten and some things don't get erased. Reproducible: Always Steps to Reproduce: Go to the url. In the table for the second bug report, 1. Click 'two'. 2. Click 'child of two!!' (the second one) 3. Click 'child of two' This always causes a problem, but sometimes the problems appear earlier. Actual Results: You'll see the last row not erased, while the paragraph of text below it overwrites it (the row that was not erased). You'll notice some other table rows did not get erased or updated properly. Expected Results: If you edit the javascript to use "block" instead of "table-row" when setting the CSS style, try it out in IE 5. Basically it should draw cleanly. If the images cannot be found, it does some extra rendering steps and tends to fix itself a bit. If you resize the window to cause a refresh, the table looks correct. Try to compare the difference between the table at the bottom of the page and the one in the middle. It still draws wrong but the difference in what it screws up may be useful.
testcase worksforme on linux, build 2001-03-28-08 and a CVS build from 2001-03-21
Assignee: akhil.arora → kmcclusk
Component: Java APIs for DOM → Compositor
QA Contact: rajendra.pallath → petersen
With the April 3rd build (2001040309), this problem nolonger occurs.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.