Open Bug 652030 Opened 9 years ago Updated 9 years ago

nsRefreshDriver::Thaw leaves nsRefreshDriver::MostRecentRefresh() returning inaccurate value for a short time

Categories

(Core :: Layout, defect)

defect
Not set

Tracking

()

People

(Reporter: dbaron, Unassigned)

Details

As discussed in bug 650469 comment 4 through bug 650469 comment 10, nsRefreshDriver::Thaw breaks the invariant (otherwise fixed by the patch in bug 650469) that nsRefreshDriver::MostRecentRefresh() should always return the most recent refresh time that it's given any refresh observer that's been registered since before that time.

We should perhaps fix this by making Thaw() notify observers, if it's safe to run script during Thaw().

(It's also possible that this invariant isn't really useful, because one refresh observer might get touched during the notification of another earlier one, and still get confused.)
You need to log in before you can comment on or make changes to this bug.