Closed Bug 289829 Opened 19 years ago Closed 19 years ago

Preferences-->Privacy-->Saved Forms Should Have a View Saved Form Data Button

Categories

(Toolkit :: Form Manager, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 279188

People

(Reporter: hociman, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050410 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050410 Firefox/1.0+

I made the mistake of incorrectly typing in text in a form field.  Whenever I
visit that site and begin to type in that field, it wants to auto-complete it
with incorrect data.  I thought I would simply delete the incorrect data in the
Saved Forms preference pane.  This is not possible.  It should be.

Reproducible: Always

Steps to Reproduce:
1.  Go to Preferences-->Privacy-->Saved Forms
2.  Look for a View Saved Form Data button
3.

Actual Results:  
All you can do is clear all saved form data.  This is too broad an action.

Expected Results:  
A View Saved Form Data button that allows you to clear the data on selected
forms, much like you can erase certain passwords from memory in
Preferences-->Privacy-->Passwords-->View Saved Passwords.
OS: MacOS X → All
Hardware: Macintosh → All
Normally you select what you want to delete in the autocomplete dropdown and you
shift/delete => the entry is gone for ever. No need for extra UI IMHO
Could you be more specific?  Hovering over an entry and pressing shift+delete doesn't do a thing.
try shift + del ? Maybe what you see is bug 271692 ?
Can't be more specific than that: To delete an autocomplete entry on a form
field, you select the entry in the autocomplete list, then you type shift +
delete or shift + del
Duplicate of bug 279188?
Yes, I would say this is a duplicate.  Marking as such.

*** This bug has been marked as a duplicate of 279188 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.