[Webkit-unassigned] [Bug 33931] New: pushstate() from within a popstate handler might lead to improper scroll/view state being incorrect later
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jan 20 18:07:13 PST 2010
https://bugs.webkit.org/show_bug.cgi?id=33931
Summary: pushstate() from within a popstate handler might lead
to improper scroll/view state being incorrect later
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: P2
Component: Page Loading
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: beidson at apple.com
pushstate() from within a popstate handler might lead to improper scroll/view
state being incorrect later
See the test case in https://bugs.webkit.org/show_bug.cgi?id=33830 for
reference.
Since the popstate event - fired from within FrameLoader::loadInSameDocument()
called from FrameLoader::navigateWithinDocument() - can effectively change the
current history item, the later call to
history()->restoreScrollPositionAndViewState() will be operating on the wrong
"current history item" from the perspective of the load.
There's a lot of complexity here in getting this precisely right, especially
since popstate events might nest and we'd probably only want to restore the
scroll/view state from the most recently popped item.
--
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