Thank you for your post.
If you are searching for any special or non-alpha-numeric characters, the character must either in quotes by itself, or use a backslash preceding the character within a string. Another option, is if you know the entire email address, is to precede the string with two equal signs (==).
Using firstname.lastname@example.org as an example, the following will find the record:
Yes, I understand, thank you, but missing the point. If auto-complete finds the correct email address but accepting auto-complete does not find records as expected there is a problem. Emails are a common enough entry that this should matter.
So that I better understand your suggestion, do you want a separate Email type field? Do you want a separate preference setting for Text fields to treat "@" character as a non-special character? It's probably best that you post this suggestion to our Product Ideas board at: Product Ideas
The Product Ideas board is monitored by Product Management and Development. Each suggestion is discussed and considered for possible implementation in a future release.
I will post to Product ideas as you suggest, but in this case I suggest that there is an inconsistency in the current implementation.
If the result of a search displays correctly based on auto-complete, referencing the existing stored content in this field, then the
user has every expectation that the search conducted as a result of this entry will return records corresponding to the auto complete.