[Webkit-unassigned] [Bug 54517] Ensure loading has stopped in HistoryController::goToItem
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Feb 18 14:57:46 PST 2011
https://bugs.webkit.org/show_bug.cgi?id=54517
--- Comment #15 from Charles Reis <creis at chromium.org> 2011-02-18 14:57:46 PST ---
(In reply to comment #13)
> (From update of attachment 82993 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=82993&action=review
>
> > Source/WebCore/page/Page.cpp:-347
> > - databasePolicy = DatabasePolicyContinue;
>
> I think with this change we no longer need DatabasePolicyContinue (or the whole enum), since we always stop databases when stopping loads. Perhaps add a FIXME to FrameLoader::stopAllLoaders to remove that option?
Looks like you're right-- added.
>
> > LayoutTests/http/tests/navigation/resources/forward-to-fragment-fires-onload-2.html:31
> > + setTimeout(function() {
>
> If it's important that this happen after after the page finishes parsing (any ideas why?), doing it in a DOMContentLoaded event listener seems more reliable than a setTimeout 0.
Yep, that works. Not sure why it doesn't work before DOMContentLoaded, since it doesn't trigger a stopAllLoaders and the stack trace from History::goToItem looks the same either way.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list