Bug 17333

Summary: pages in iframes are not always stored in the history object
Product: WebKit Reporter: Benny Vluggen <b.vluggen>
Component: HistoryAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: dacarson, mihaip, priyajeet.hora
Priority: P2    
Version: 523.x (Safari 3)   
Hardware: PC   
OS: Windows XP   
URL: http://positionabsolute.net/projects/javascript/TiteSite/index.php
Attachments:
Description Flags
Reduction none

Benny Vluggen
Reported 2008-02-12 13:38:40 PST
There are several problems with iframe content: - if Safari is started and then page with the iframe is the first page to be loaded then it won't be added to the history object nor will any subsequent pages that are loaded from the main page in the iframe. - if Safari is started and for example the Apple homepage is first loaded and then the site with the iframe page then the iframe pages are added to the history object but when you hit the back button till you reach the first page that was loaded in the iframe then next back button action should lead you back to the Apple page but instead you are stuck no matter how often you click back you won't get to the Apple page
Attachments
Reduction (507 bytes, text/html)
2008-09-02 11:34 PDT, David Carson 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
David Carson
Comment 1 2008-09-02 11:34:36 PDT
Created attachment 23121 [details] Reduction The attached file will show the first issue that is mentioned in this bug. To reproduce, load the site. Click Test1, when Apple.com is loaded in the iFrame, click Test2. When Google is loaded, press the back button. It does not take you back to the iFrame containing Apple.com
Darth
Comment 2 2010-09-27 13:58:31 PDT
Seems like this issue has been fixed in the latest webkit release. However Safari 5 still has this issue.
Mihai Parparita
Comment 3 2010-09-29 17:33:10 PDT
http://trac.webkit.org/changeset/61207 most likely is what fixed this (as comment 2 indicates, this no longer happens in WebKit nightlies).
Note You need to log in before you can comment on or make changes to this bug.