Closed Bug 713407 Opened 9 years ago Closed 9 years ago

Account provisioner does not find any possible email addresses unless the search text contains a space

Categories

(Thunderbird :: Mail Window Front End, defect)

10 Branch
x86
Windows XP
defect
Not set
major

Tracking

(thunderbird10-, thunderbird11+ fixed)

RESOLVED FIXED
Tracking Status
thunderbird10 - ---
thunderbird11 + fixed

People

(Reporter: unicorn.consulting, Assigned: sancus)

References

Details

The account provisioner does not locate any possible email addresses unless the search string contains a space, although the dialog text indicates "Just fill in your first and last name, or any other words you’d like, in the fields above to get started"

madmat  returns a sorry

mad mat returns a variety of options

Expected result:
Both search string should return the same or very similar results.

Have set the severity of this to Blocker, as this is I think a show stopper for the feature and needs correction whilst still in beta.
Blocks: 686347
Sev: Major. Please see <https://bugzilla.mozilla.org/page.cgi?id=fields.html#importance>
I agree that the account provisioning feature is severely impaired by this bug.
Severity: blocker → major
Ack, this is a pretty major oversight.  Sorry it slipped through - on it.
Assignee: nobody → mconley
Status: NEW → ASSIGNED
Hm - ok, so this doesn't appear to be on the client-side.  The suggestFromName service being hosted by Mozilla doesn't appear to like it if there's no last name provided.

Example:

https://broker-live.mozillamessaging.com/provider/suggest?first_name=Mike&last_name=&providers=aol,hover,yandex

Sancus - is it safe to assume that when we switch to the real suggestion service, it'll handle the case where there is no last name?

-Mike
Assignee: mconley → nobody
Status: ASSIGNED → NEW
Assignee: nobody → sancus
This feature has been postponed until TB 11, so we don't need this yet, but we can test it when we're ready.
This should be fixed now. The issue was that empty last_name or first_name arguments were being interpreted as not submitted parameters at all.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.