Closed
Bug 1071314
Opened 11 years ago
Closed 11 years ago
document.open() and write() in an iframe prevents back button from working
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: eml-bugzilla, Unassigned)
Details
Attachments
(1 file)
|
212.09 KB,
video/mp4
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.122 Safari/537.36
Steps to reproduce:
(go http://demo.feed.fm/ffbug/outer.html to try this)
Browse the file outer.html that just holds an iframe:
<body>
<iframe src="index.html"></iframe>
</body>
The "index.html" file uses document write to alter itself:
<body>
<script>
setTimeout(function(){
window.document.open("text/html", "replace");
window.document.write('<html><body>This is the index page. Go to <a href="2.html">page 2</a></body></html>');
window.document.close();
});
</script>
The user now clicks on the 2.html link to visit this page:
<body>
Try to go back to the previous page
</body>
The user should now click on the back button to try to get back to viewing the 'index.html file in the iframe.
Actual results:
The iframe doesn't change when the user clicks the back button.
Expected results:
The iframe should render the contents of the 'index.html' file in the iframe.
WFM with FF35 on WIN7.
Did you test with a fresh profile?
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Anyway, it could be an issue specific to the Mac version.
Flags: needinfo?(eml-bugzilla)
|
Reporter | |
Comment 2•11 years ago
|
||
Oh wow - trying with a fresh profile fixed it, although I don't understand why. Perhaps it's because the new profile doesn't have plugins that might be affecting things? I'll play around with it some more. Thanks for the suggestion!
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(eml-bugzilla)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•