Bug 9148 – Setting location.href is not registered in history

• Component: History
• Status: RESOLVED FIXED

[David Kilzer (:ddkilzer)]

Setting location.href to load a page does not cause that URL to be recorded in the history.  When a link to the previously loaded page appears later, that link is rendered as unvisited rather than visited.

In Firefox 1.5.0.3 on Mac OS X, a page loaded via location.href is recorded in history.

In MSIE 6 on WinXP SP2, a page loaded via location.href is also recorded in history.

This behavior occurs in Safari 2.0.3 (417.9.3) on Mac OS X 10.4.6 (8I127) as well as locally-built WebKit r14551.

[David Kilzer (:ddkilzer)]

Created attachment 8578 [details]
Test v1

Test demonstrating the problem with setting location.href.  It may be possible to simplify this test.

[Brady Eidson]

I'm quite interested to know what the actual correct behavior is.  I know that Safari 2.0 and ToT both act differently from FFX, which puts all 3 items in history, but do we know which is actually "correct"?

[David Kilzer (:ddkilzer)]

(In reply to comment #2)
> I'm quite interested to know what the actual correct behavior is.  I know that
> Safari 2.0 and ToT both act differently from FFX, which puts all 3 items in
> history, but do we know which is actually "correct"?

NOTE: I filed this bug because I noticed a difference in behavior between Safari/WebKit, Firefox and MSIE 6.  I do not know what the correct behavior is.

[Beth Dakin]

<rdar://problem/5257045>

[David Kilzer (:ddkilzer)]

This bug was not fixed by the fix for Bug 13400.

[David Kilzer (:ddkilzer)]

May be fixed by:  http://trac.webkit.org/projects/webkit/changeset/24353

[David Kilzer (:ddkilzer)]

(In reply to comment #6)
> May be fixed by:  http://trac.webkit.org/projects/webkit/changeset/24353

This appears to be fixed now.  (The test case doesn't work with DRT, but it works in Safari.)