User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 When entering an email address TB does email completion and either shows a list of matching emails or automatically fills an only matching one. However this is not done any more after the "@" character is typed. This is very bad and I cannot think of a reasonable justification for this. I have many email addresses that only differ in the hostname part. Having the completion mechanism continue after the "@" would greatly simplify entering the correct address. Why does TB force me actually type in the hostname once I have typed the "@"? Reproducible: Always Steps to Reproduce: 1. enter an email address where the completion list shows several address with the same name before the @ and different hostnames after the @. 2. once you enter the @ character the completion list disappears and no completion is done any more, forcing you to either backtrack or type the whole address manually

Dupe of bug 234422.

This is NOT a DUPE of bug 234422 Bug 234422 requests that any substring of the address can be used for autocompletion, not just the leading part which is semantically different from what is done now. This bug just requests that - while maintaining the leading substring semantics - completion will be done for *any* leading substring not just the substing before the @ symbol. Changing the semantics could be a useful enhancement or not. But this is simply a bug because the way how it is done now is implemented in an incomplete manner, stopping at an arbitrary position.

See also bug 95631. *** This bug has been marked as a duplicate of 200804 ***

Why is this a "Core" bug and not a TB bug? Isn't this an issue of the UI that could (and maybe will) get handled differently in e.g. Seamonkey and TB?

(In reply to comment #4) > Why is this a "Core" bug and not a TB bug? Isn't this an issue of the UI that > could (and maybe will) get handled differently in e.g. Seamonkey and TB? I suppose it *could* but currently the widget's logic resides in core code, and there's no need to fork it.