Bug 15786
Summary: | REGRESSION: embedded iframes whose contents are loaded by window.onload should NOT add back entry | ||
---|---|---|---|
Product: | WebKit | Reporter: | Alex Plank <alex> |
Component: | History | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | alex, ap, emacemac7, grahamperrin, webkit |
Priority: | P1 | Keywords: | InRadar, Regression |
Version: | 523.x (Safari 3) | ||
Hardware: | Mac | ||
OS: | OS X 10.4 | ||
URL: | http://www.wrongplanet.net/ |
Alex Plank
This causes the back button to be unusable (pressing it merely generates more history entries) on sites which use an onload event to load one or more pages through an iframe. Example can be found on the url listed.
Steps to reproduce:
1)go to URL ( www.wrongplanet.net ),
2)navigate the site
3)attempt to go back by pressing the browser's back button
this may or may not be related to bug 14438
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Alex Plank
this is on 10.5
David Kilzer (:ddkilzer)
Confirmed with a local debug build of WebKit r27373 with Safari 3 Public Beta v. 3.0.3 (522.12.1) on Mac OS X 10.4.10 (8R218).
David Kilzer (:ddkilzer)
Works in Safari 2.0.4 (419.3) with original WebKit on Mac OS X 10.4.10 (8R218), so this is a regression.
The earliest nightly build (r11976) displays the buggy behavior as well.
Safari 3 Public Beta for Windows on XP Pro SP2 has the same issue.
In Opera 9.22 and Firefox 2.0.0.8 on Mac OS X 10.4.10, you must click back TWICE to go back one page (although you're not stuck reloading the same page like you are with WebKit/Safari).
Works in MSIE 7 on Windows XP Pro SP2.
David Kilzer (:ddkilzer)
<rdar://problem/5619340>
Robert Blaut
(In reply to comment #4)
> <rdar://problem/5619340>
>
Is the reported URL still hurt by this issue? I cannot reproduce described issue on the www.wrongplanet.net site.
I'm not sute but the bug is probably related to bug 12993.
Alex Plank
Robert,
I changed the method of loading iframes on the listed url due to safari users complaining about the bug. I will try to make a specific page that demonstrates the issue.
Alexey Proskuryakov
Marking as INVALID, because there is no way to investigate this issue, now that the site has been changed. Please feel free to re-open if you can provide a test case.