Bug 32156
| Summary: | Browser history inconsistent when changing location.hash in an Iframe child document | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | "Cowboy" Ben Alman <cowboy> |
| Component: | History | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Major | CC: | aroben, bartzy, beidson, christopher.ricca, hgweb2, mihaip, ryan |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://benalman.com/code/projects/jquery-bbq/examples/bug-webkit-hash-iframe/ | ||
"Cowboy" Ben Alman
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 3.0.195.33 / OS X Webkit nightly r51669
Synopsis:
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:
http://benalman.com/code/projects/jquery-bbq/examples/bug-webkit-hash-iframe/
This may be related to bugs 14959 and 17333, but I felt this description was sufficiently different to warrant a separate ticket.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Hamish
I have also come across this. Other major browsers like Firefox and IE 6/7/8 all work correctly.
Bar Ziony
I also came across this.
Why this is not getting any attention ?
Thanks,
Bar.
Mihai Parparita
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 ***