Closed Bug 42892 Opened 25 years ago Closed 24 years ago

FlushPendingNotifications() should only flush reflows if needed

Categories

(Core :: Layout, defect, P3)

Product:
Core
Component:
Layout
Type:
defect

Tracking

()

Status:
VERIFIED FIXED
Milestone:
mozilla0.8

People

(Reporter: pollmann, Assigned: pollmann)

References

Details

(Keywords: perf)

Attachments

(2 files)

patch (reverse)
37.49 KB, patch
Details | Diff | Splinter Review
patch (ignore above)
7.70 KB, patch
Details | Diff | Splinter Review
Per Johnny's note on bug 4891, we should split this up (add a parameter) into flushing content changes only, and flushing both content changes and reflows We could then look at the callers to see who might gain performance benefits from only flushing content changes.
I have a first pass at this done in my tree, the diff is not large.
Status: NEW → ASSIGNED
Keywords: perf
Target Milestone: --- → M18
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.
Target Milestone: M18 → Future
Set milestone to mozilla0.8
Target Milestone: Future → mozilla0.8
Attached patch patch (reverse) — — Splinter Review
Fix checked in. This bug can not be (easily) verified by running the program.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Marking verified per last comments.
Status: RESOLVED → VERIFIED
*** Bug 52892 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: