[Webkit-unassigned] [Bug 48809] Update correct content state during back/forward navigations

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Nov 15 16:13:14 PST 2010


--- Comment #33 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2010-11-15 16:13:14 PST ---
> Yes, with my change to setCurrentItem, it still works in most cases if we revert the FrameLoader change and don't clear m_previousItem in updateForFrameLoadCompleted.  There's a few layout tests that crash or fail now (e.g., due to the ASSERT in recursiveGoToItem), but I'll take a closer look at the assumptions to see if I can fix them.


> For reference, I'm seeing fast/history/history-back-within-subframe-hash.html crash and fast/history/saves-state-after-fragment-nav.html fail.


My thinking here is that if we keep pulling on this thread that we'll find that things can be simpler, which would be good.

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