Closed
Bug 519590
Opened 16 years ago
Closed 16 years ago
Investigate not interrupting reflow until enough time has elapsed
Categories
(Core :: Layout, defect, P1)
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| status1.9.2 | --- | beta1-fixed |
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
(Depends on 1 open bug)
Details
Attachments
(2 files)
|
5.22 KB,
patch
|
Details | Diff | Splinter Review | |
|
7.77 KB,
patch
|
roc
:
review+
|
Details | Diff | Splinter Review |
Work-in-progress patch attached.
| Assignee | ||
Updated•16 years ago
|
| Assignee | ||
Comment 1•16 years ago
|
||
This does depend on bug 519590. Only tested on Mac so far; will test elsewhere too.
Disabling interrupts in chrome was just something I thought we should do; please let me know if you think we shouldn't....
Attachment #404111 -
Flags: review?(roc)
Comment on attachment 404111 [details] [diff] [review]
With joel's help, a fix that actually works.
Add "using mozilla::TimeStamp;", "using mozilla::TimeDuration;" to the top of nsPresContext.cpp instead of repeating the mozilla:: prefix?
Attachment #404111 -
Flags: review?(roc) → review+
| Assignee | ||
Comment 3•16 years ago
|
||
Pushed http://hg.mozilla.org/mozilla-central/rev/e9d59855daf9 with that change.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 4•16 years ago
|
||
I think this should be a beta blocker. It's a change that we really need beta
testing on (and conversely, beta testing without this change is much less
useful).
Flags: blocking1.9.2?
Priority: -- → P1
| Assignee | ||
Updated•16 years ago
|
Attachment #404111 -
Flags: approval1.9.2?
Assignee: nobody → bzbarsky
Updated•16 years ago
|
Flags: blocking1.9.2? → blocking1.9.2+
| Assignee | ||
Comment 5•16 years ago
|
||
status1.9.2:
--- → beta1-fixed
Attachment #404111 -
Flags: approval1.9.2?
You need to log in
before you can comment on or make changes to this bug.
Description
•