[Webkit-unassigned] [Bug 30224] New: Fragment scrolls initiated by javascript should not add a history item
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Oct 8 11:11:58 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=30224
Summary: Fragment scrolls initiated by javascript should not
add a history item
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: History
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: phanna at email.unc.edu
Currently, going to m.cnn.com will trigger a javascript location change to
m.cnn.com/#___1__ adding a history item for both m.cnn.com and the fragment
scroll. Neither Chrome nor Firefox does this (Chrome happens to use its own
history list rather than WebKit's).
I believe the fix should be around FrameLoader.cpp:3484. An additional check
for a user initiated click would avoid adding the extra history 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