Open Bug 306337 Opened 14 years ago Updated 8 years ago

Pressing Shift+Delete on a drop-down contact suggestion should (prompt to) delete the suggested contact

Categories

(Thunderbird :: Message Compose Window, enhancement)

enhancement
Not set

Tracking

(Not tracked)

People

(Reporter: stpmoz, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; da-DK; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; da-DK; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

I mostly use the collected addresses in the address book for word completion
when entering new receivers in to:, cc: or bcc:. Therefore, it would be great if
I could delete contacts in the address book directly from the drop down contact
suggestion.

Reproducible: Always

Steps to Reproduce:
1. Start typing e-mail or name for contact in to:,cc: or bcc:
2. A list of suggestions will drop down
3. Press down arrow until you find a deprecated contact
4. Press Delete

Actual Results:  
Nothing

Expected Results:  
The contact should be deleted.
Delete shouldn't delete it - it should be Shift+Delete.

Shift+Delete deletes autocomplete suggestions from the location bar in Firefox,
but it doesn't delete their associated history entries. It also deletes
autocomplete suggestions in web forms; but here the data (the text) is
completely removed.

I'm not sure whether Shift+Delete should delete contacts. I suppose it would
make sense if it deleted contacts that were collected, but just deleted the
suggestion for manually-added contacts.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Summary: Pressing Delete on a drop-down contact suggestion should (prompt ) delete the suggested contact → Pressing Shift+Delete on a drop-down contact suggestion should (prompt to) delete the suggested contact
*** Bug 321648 has been marked as a duplicate of this bug. ***
attn Mark :)
QA Contact: message-compose
Assignee: mscott → nobody
You need to log in before you can comment on or make changes to this bug.