Closed Bug 277231 Opened 20 years ago Closed 20 years ago

writing content generated by javascript into iframe ads pages to history and breaks back button

Categories

(Core :: DOM: Navigation, defect)

1.7 Branch
x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: info, Unassigned)

References

()

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041122 Firefox/1.0

i have a javascript function HighlightSearchTerms() which writes content into 
document.body:

bodyText = HighlightSearchTerms(bodyText);
document.body.innerHTML = bodyText;

When calling the script, it also writes content into the iframes on that page.
This adds pages to the browser history (number of iframes = number of 
additional entries in history) and renders the back button of the browser 
useless. Same happens when calling a form in an iframe. this does serious 
trouble. example: remote scripting with location.replace()

Reproducible: Always

Steps to Reproduce:
1. go to http://www.dancefloorstars.de
2. use the search box
3. look at the browser history and try to use the back button

Actual Results:  
browser back button not working
javascript:history.go(-1) etc. not working

Expected Results:  
do not add identical pages to browser history. When calling iframes, no 
additional pages should be written into history.
Added: Script deactivated because of Mozillas different "innerHTML" 
interpretation. So, bug not reproducable at this time (high traffic website).
Assignee: bugs → nobody
Component: History → History: Session
Product: Firefox → Core
QA Contact: mozilla → core.history.session
Version: unspecified → 1.7 Branch
If it's not reproducible, we can't do anything about it.  Marking invalid, since
there is no way to reproduce the bug.  Please reopen when there is a page or
testcase attached to the bug that can be used to reproduce

Note that a bug with a very similar description has been fixed since Firefox
1.0, so you may want to retest with a current trunk build.  I'll bet even money
that this is fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
You need to log in before you can comment on or make changes to this bug.