Closed Bug 206958 Opened 21 years ago Closed 21 years ago

Form content is always deleted when using the back button and then using the forward button

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: ivo.frass, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.3) Gecko/20030312

When filling a form I sometimes use the "back" button to have a look on the last
viewed side for information. When I then use the "forward" button to go to the
form again, the form content is deleted. With mozilla 1.0 I don´t have this
problem. 

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Reporter, try using a more recent build of Mozilla (1.4b perhaps).  I've never 
observed this behavior, though I have seen form data persist thru a refresh :)
Summary: form content is always deletet when using the back button and then using the forward button → form content is always deletet when using the back button and then using the forward button
ivo.frass: Do you still have this problem in more recent Mozilla builds? Perhaps
this has been fixed. Another possibility is that the particular site you visit
has code that clears the form each time the page is viewed, unless this happens
to you at all sites that use forms. Do you have a URL we could try? Please let
us know if this is still a problem for you. Thanks.
Summary: form content is always deletet when using the back button and then using the forward button → Form content is always deleted when using the back button and then using the forward button
Closing 5+ month old bug as WFM. But if you can reproduce this bug in a recent
Mozilla build, please feel free to reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.