[Webkit-unassigned] [Bug 25570] WebKit incorrectly fires scroll events during the history.{back, forward, go} call when navigating to a reference fragment

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=25570





------- Comment #2 from fishd at chromium.org  2009-05-05 10:47 PDT -------
The code in FrameLoader::scheduleHistoryNavigation is what I am suggesting
should perhaps change.  If the URL we are at and the URL we are navigating to
differ only in reference fragment, then the code calls goBackOrForward directly
instead of calling scheduleRedirection.  This results in the navigation
occurring synchronously, which leads to scroll events being dispatched during
the history.{back,forward,go} call.  That in turn means that JavaScript is
getting re-entered, which may be quite unexpected by some web applications.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.