Closed
Bug 308493
Opened 19 years ago
Closed 19 years ago
AutoComplete Needs Refinement & Customization
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: selowitch, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 When filling in e-mail addresses automatically, Thunderbird does some odd things like offer e-mail addresses that are no longer in the Address Book (or never were). There also seems to be no way to specify a default e-mail address for a specific Display Name. Reproducible: Always Steps to Reproduce: 1. Begin typing an address in the To, CC, or BCC field(s). 2. Notice that the list of autocomplete possibilties that pops up is not what you would like it to be. Expected Results: I would prefer that there be an option to a) offer only current Address Book entries during AutoComplete; b) offer only the default e-mail address for the display name being typed; c) ability to edit the cache of autocomplete address manually.
Comment 1•19 years ago
|
||
Have you checked to make sure that the names you thought were purged aren't in, for instance, the Collected Addresses? And you're not configured to use an LDAP server? I've never seen any autocompletion for an address that wasn't somewhere in the address book. As for a "default email address": is bug 116006 what you're describing?
Probably related (if not, let me know, I'll file a separate bug). I'm trying to send an email to someoone who has attempted to despam their email by corrupting the link. I paste in the raw text into the address bar: mailto:trueg(at)k3b.org It then appends @somesite.com and highlights it. I press backspace to remove this, because this is NOT what I want. The moment I then press the arrow key to head to the (at) and remove it, it reappends @somesite.com. !#%% I manually clear it. This time, I hit home, and procede to delete mailto:. The moment I finish clearing it, and press the right arrow to head to that (at), the text field resets from: trueg(at)k3b.org to: mailto:trueg(at)k3b.org@somesite.com At this point, I'm questioning whether the person who wrote this realizes how angry this is making me. A quick whip through the edit -> preferences shows a nice option to choose where it autocompletes from, but not to turn off autocomplete, nor a description why using arrow keys will cause the text field to reset to the (stupid, un-useful) content I am trying to clean up.
Comment 3•19 years ago
|
||
(In reply to comment #2) > I paste in the raw text into the address bar: > mailto:trueg(at)k3b.org > It then appends @somesite.com and highlights it. I press backspace to remove > this, because this is NOT what I want. > The moment I then press the arrow key to head to the (at) and remove it, it > reappends @somesite.com. > > I manually clear it. This time, I hit home, and procede to delete mailto:. > The moment I finish clearing it, and press the right arrow to head to that > (at), the text field resets from: > trueg(at)k3b.org > to: > mailto:trueg(at)k3b.org@somesite.com > [...] > A quick whip through the edit -> preferences shows a nice option to choose > where it autocompletes from, but not to turn off autocomplete This is bug 131692, duped to bug 93453 because the fix for that bug provides the option to turn off completion-with-domain entirely, on a per-identity basis. This option is recent, and there is no UI for setting the preference. Also, it's slightly broken in TB 1.5; see bug 326280. Without turning off completion-to-domain, the quick workaround to your particular problem is: after pasting, *first* select the "(at)" and type "@"; then you can complete your other edits without further bogus autocompletion. Less than ideal, true. Sam Elowitch: the questions from comment 1 are still open.
Comment 4•19 years ago
|
||
No response from reporter => Invalid Sam Elowitch, feel free to reopen, but provide a response to comment 1.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•