setComposeDetails handling of commas in address names
Categories
(Thunderbird :: Add-Ons: Extensions API, defect)
Tracking
(thunderbird_esr78+ fixed, thunderbird81 affected)
People
(Reporter: musiquegraeme, Assigned: darktrojan)
References
Details
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
wsmwk
:
approval-comm-esr78+
|
Details | Review |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:80.0) Gecko/20100101 Firefox/80.0
Steps to reproduce:
I started an email and one of the addresses was in the form Name, job <address>
I pressed send and my addon uses setComposeDetails to expand addresses.
Actual results:
setComposeDetails (in the compose API) expanded the address but now it was Name <> in pink. The address was sent correctly to setComposeDetails but it took the comma between name and job as indication of a new address and so somehow removed the rest of the "name" and the address.
Expected results:
It should have handled the comma in the name as part of the name and not an indication to start a new address.
Comment 1•4 years ago
|
||
(In reply to musiquegraeme from comment #0)
I started an email and one of the addresses was in the form Name, job <address>
I pressed send and my addon uses setComposeDetails to expand addresses.
Can you give an example of "expanding" addresses?
Updated•4 years ago
|
Reporter | ||
Comment 2•4 years ago
|
||
Not really significant - the point was simply that setComposeDetails took the addresses that were in getComposeDetails and mishandled any commas in the name. I just did another test where there was no mailing list entry but the addon got the details with getComposeDetails and then sent the same addresses back with setComposeDetails and turned an address with a comma in the name like Name , job <Address> into Name <>
Of course the answer to your question is that the addon in question PopMailListRecipients 2 and expands any mail lists in the addresses to the component emails.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 4•4 years ago
|
||
Instead of just using strings as-is, use the header parser to read and reformat them. This resolves issues with commas.
Assignee | ||
Updated•4 years ago
|
Pushed by thunderbird@calypsoblue.org:
https://hg.mozilla.org/comm-central/rev/221920c8e758
Correctly interpret addresses passed as strings to setComposeDetails. r=mkmelin
Pushed by geoff@darktrojan.net: https://hg.mozilla.org/comm-central/rev/db01f53031b8 follow-up - Fix a missed review comment. rs=me DONTBUILD
Updated•4 years ago
|
Comment 7•4 years ago
|
||
Comment on attachment 9173951 [details]
Bug 1663009 - Correctly interpret addresses passed as strings to setComposeDetails. r?mkmelin
[Approval Request Comment]
WX API correctness fix. Definitely should go to 78
Comment 8•4 years ago
|
||
Comment on attachment 9173951 [details]
Bug 1663009 - Correctly interpret addresses passed as strings to setComposeDetails. r?mkmelin
[Triage Comment]
Approved for esr78
Comment 9•4 years ago
|
||
bugherder uplift |
Description
•