Closed Bug 229980 Opened 16 years ago Closed 16 years ago

Inconsistent page on Back/Forwards


(Core :: DOM: Navigation, defect)

Windows 2000
Not set





(Reporter: jsfbbz, Assigned: bugzilla)



(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

When a page is modified via Javascript, then you navigate Back, then Forwards to
return to the page, input elements will have the values as last seen, but other
elements will be returned to their default page-load state.

Reproducible: Always

Steps to Reproduce:
1. Go to some random web page to prime history
2. See attachment.
3. Check, Do, Check, Back, Forwards, Check

Actual Results:  

Expected Results:  

I wouldn't have been too suprised by "Old/Old/Old" for the final state, but
would prefer "New/New/New". In my mind navigation should return you to an exact
copy of the DOM the last time you were at that page in the history.

(The original page, btw, is to edit a database object with several simple
attributes, which are edited in normal form fields, plus a link to another
database object which can't really be simply typed in. The JS pulls up another
form to find a new object to link to and sets the link text to an object
description, link href to info about the target object, and hidden field to the
database key for the new object. Accidental navigation then produces confusing
results since we do actually have the new target key, but the user *sees* the
old values and thinks the change has been discarded.)
Attached file Test case
Not Firebird-specific.
Component: History → History: Session
Product: Firebird → Browser
Version: unspecified → Trunk
I see this also.  Dupe of Bug 38486 via bug 189824.

*** This bug has been marked as a duplicate of 38486 ***
Closed: 16 years ago
Resolution: --- → DUPLICATE
Component: History: Session → Document Navigation
QA Contact: mozilla → docshell
You need to log in before you can comment on or make changes to this bug.