Closed Bug 96114 Opened 24 years ago Closed 23 years ago

fail reloading form values

Categories

(Core :: DOM: Core & HTML, defect, P1)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
All
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 46845
Milestone:
mozilla0.9.5

People

(Reporter: jakub, Assigned: radha)

References

(
URL
)

Details

(Keywords: dataloss)

when defined value of form is rewritten by new value, then RELOAD is hitted, mozilla fails to insert original value to form input. step by step: 1) make simple <FORM> and input for example: <INPUT TYPE="TEXT" NAME="name" VALUE="jakub@salon.cz"> 2) access page with form with mozilla 3) rewrite value jakub@salon.cz with anything other. do not click submit 4) hit RELOAD button 5) page still contains rewrited value instead of jakub@salon.cz it is probably good behave, but when one rewrite original value with nothing (blank) and hits reload, the value is still blank screenshot available...
->form submission.
Assignee: asa → rods
Status: UNCONFIRMED → NEW
Component: Browser-General → Form Submission
Ever confirmed: true
QA Contact: doronr → vladimire
I don't see this on WinNT
Status: NEW → ASSIGNED
Priority: -- → P1
Summary: fail reloading form values → [LNX]fail reloading form values
Target Milestone: --- → mozilla0.9.5
I cannot reproduce with a local file, but can reproduce with HTTP on Win NT (2001-08-26-08). Does not occur with shift+reload, though. This causes dataloss on Bugzilla. If you reload a bug and someone else has changed something like the summary, you'll get still the old summary. If you add a comment, you'll change the summary to the old value too. Probably this is basically the same as bug 81504.
Severity: major → critical
Keywords: dataloss
OS: Linux → All
Summary: [LNX]fail reloading form values → fail reloading form values
Bug 60269, bug 46845 and maybe bug 79063 are very similar too. If you dupe this one to 46845, please note that it's futured, which seems not to reflect the actual severity.
Radha is this in your area, I think we are doing this on purpose.
Assignee: rods → radha
Status: ASSIGNED → NEW
This is same as 81504 *** This bug has been marked as a duplicate of 81504 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Doesnt look like a duplicate to me... That bug deals with reloading default values into wrong fields, and this one deals with not reloading default values....
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
This is dupe of 46845 though... *** This bug has been marked as a duplicate of 46845 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
verifying
Status: RESOLVED → VERIFIED
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.