Bug 32156 - Browser history inconsistent when changing location.hash in an Iframe child document
Summary: Browser history inconsistent when changing location.hash in an Iframe child d...
Status: RESOLVED DUPLICATE of bug 40451
Alias: None
Product: WebKit
Classification: Unclassified
Component: History (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Major
Assignee: Nobody
URL: http://benalman.com/code/projects/jqu...
Depends on:
Reported: 2009-12-04 06:45 PST by "Cowboy" Ben Alman
Modified: 2010-09-07 11:15 PDT (History)
7 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description "Cowboy" Ben Alman 2009-12-04 06:45:35 PST
When the location.hash is changed in a document loaded in an Iframe, history entries are not always created correctly. This has been tested in OS X Safari Version 4.0.4 (5531.21.10) / Windows Chrome / OS X Webkit nightly r51669


Given an Iframe like this: <iframe src="page.html#begin"></iframe>

If that page.html location.hash is then set to #middle and #end, when the back button is pressed, #middle can be reached, but #begin cannot.

This page has a complete description and working example:

This may be related to bugs 14959 and 17333, but I felt this description was sufficiently different to warrant a separate ticket.
Comment 1 Hamish 2010-04-07 07:14:36 PDT
I have also come across this. Other major browsers like Firefox and IE 6/7/8 all work correctly.
Comment 2 Bar Ziony 2010-09-06 13:41:24 PDT
I also came across this.

Why this is not getting any attention ?

Comment 3 Mihai Parparita 2010-09-07 11:15:22 PDT
I am not able to reproduce this in current WebKit nighly builds (r66819) or the current Chrome stable channel (version 6.0.472.53, cut around WebKit revision r63707).

Since I'm pretty sure that http://trac.webkit.org/changeset/61207 is what fixed this, I'm marking this as a dupe of the bug that was attached to.

*** This bug has been marked as a duplicate of bug 40451 ***