[Webkit-unassigned] [Bug 48812] FrameLoader::checkLoadCompleteForThisFrame uses wrong history item
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Nov 18 14:11:03 PST 2010
https://bugs.webkit.org/show_bug.cgi?id=48812
--- Comment #34 from Charles Reis <creis at chromium.org> 2010-11-18 14:11:03 PST ---
(In reply to comment #33)
> (From update of attachment 74161 [details])
> Why is it safe to put a HistoryItem* in this object without using RefPtr? Can’t the history item be destroyed while the NavigationAction object is still around?
I don't think it'll get destroyed before we access it in checkLoadCompleteForThisFrame, but it's probably not good to keep it that way.
I'll upload a new patch reordering the arguments to eliminate the ambiguity. The last constructor will now be:
NavigationAction(KURL, bool, FrameLoadType, PassRefPtr<Event> = 0)
I can switch it to a non-optional Event argument and passing 0 at the call sites if you'd rather have that than reordered arguments.
--
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