Closed Bug 309312 Opened 20 years ago Closed 18 years ago

form autocompletion overwrites fields retrieved from a database

Categories

(Toolkit :: Form Manager, defect)

1.7 Branch
x86
Windows 98
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 112260

People

(Reporter: tech, Assigned: dveditz)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; fr; rv:1.7.11) Gecko/20050728 Build Identifier: Mozilla/5.0 (Windows; U; Win98; fr; rv:1.7.11) Gecko/20050728 on some pages, the form autocompletion overwrites fields whether they are empty or not, even if autocomplete is off. It forbids to modify a form contain. the workaround found at http://developer.mozilla.org/en/docs/index.php?title=How_to_Turn_Off_Form_Autocompletion&redirect=no doesn't work Reproducible: Always Steps to Reproduce: 1. open a form 2. enter the password for wallet Actual Results: the form fields are filled with values used some times before, but even if I change them and save the form the same values come back again and again Expected Results: not fill the fields or ask me if I want to fill them
*** This bug has been marked as a duplicate of 270558 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Perhaps it's rather a duplicate of bug 198419 ...
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
This bug can't be a duplicate og 270558, because 270558 is a mozilla-firefox bug and 309312 is on Mozilla Application Suite
This is definitely a duplicate, though.
Whiteboard: DUPEME
==> Form manager
Assignee: nobody → dveditz
Component: XP Apps: Autocomplete → Form Manager
Product: Mozilla Application Suite → Core
Version: unspecified → 1.7 Branch
(In reply to comment #4) > This is definitely a duplicate, though. > It's a duplicate of 112260 (mozilla bug) not of 270558 (firefox bug)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago18 years ago
Resolution: --- → DUPLICATE
Product: Core → Toolkit
QA Contact: form.manager
Version: 1.7 Branch → 1.0 Branch
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.