Closed Bug 109785 Opened 23 years ago Closed 23 years ago

Posted data keeps reposting

Categories

(Core :: DOM: Navigation, defect)

x86
All
defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: raiden23, Assigned: radha)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (Windows NT 5.0; U)
BuildID:    2001101117

Ok, here's a quirk I see in Mozilla that I don't in Netscape.  If you're working 
a form, say like how we access our Oracle DB via netscape here at work, when 
you're in the notes window and you back up to see previous notes, or you back up 
to any page that was previously sent with a "POST" operation, it resends that 
data or tries to repost it when it goes back to that page.  Netscape I've 
noticed doesn't do that.  When you click back, it just shows results of the last 
post operation without reposting the same data.  Can we get that into Mozilla 
somehow?  It's getting annoying to have to keep telling it not to repost the 
data when backing up in a window.

Reproducible: Always
Steps to Reproduce:
1.  Press submit on any form.
2.  Try to back up.
3.  Gives "Info has expired, would you like to resend this data?" or something 
like that.

Actual Results:  Reposts the same data I just submitted.

Expected Results:  Just backed up to the previously submitted page(s) and shown 
the results from the post without actually reposting the form data.
Reporter: 
Can you try it again with a recent nightly build ?
It works for me with win2k build 20011111.. 
(URL: http://babelfish.altavista.com/tr)

->form submission
Assignee: asa → alexsavulov
Component: Browser-General → Form Submission
QA Contact: doronr → vladimire
This is not form sub.  Session history.
Assignee: alexsavulov → radha
Component: Form Submission → History: Session
QA Contact: vladimire → claudius
wfm -> marking worksforme
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
You need to log in before you can comment on or make changes to this bug.