Closed
Bug 1045417
Opened 10 years ago
Closed 10 years ago
Event attendee with a comma in display name gets splitted in two attendees
Categories
(Calendar :: Dialogs, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
3.3.1
People
(Reporter: viaujoc, Assigned: MakeMyDay)
References
Details
Attachments
(1 file, 1 obsolete file)
3.71 KB,
patch
|
Fallen
:
review+
Fallen
:
approval-calendar-aurora+
Fallen
:
approval-calendar-beta+
Fallen
:
approval-calendar-esr+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36 Steps to reproduce: 1. Have a contact in your address book that has a comma in the display name such as "Smith, John" with an email address (I will use jsmith@example.com here) 2. Create an event 3. Add attendees 4. As the first attendee, start typing the name of the contact mentionned at step 1. 5. Select the suggested contact (the one at step 1) Actual results: Two attendees are added to the event: First attendee: Smith (with no email address) Second attendee: John <jsmith@example.com> Expected results: There should be only one attendee: Smith, John <jsmith@example.com>
Reporter | ||
Updated•10 years ago
|
OS: All → Windows 8.1
Hardware: All → x86_64
Do you insert the two names separated with comma between double quotes when you edit the attendees dialog: "Smith, John" <jsmith@example.com> It should work fine in this case, at least, it works for me with LG 3.3.
Summary: Event attendee with a coma in display name gets splitted in two attendees → Event attendee with a comma in display name gets splitted in two attendees
Reporter | ||
Comment 2•10 years ago
|
||
When I start typing the name of the first attendee, suggestions from my address book automatically appear. If I click on one, then the attendee is immediately splitted in two lines. Strangely, when I do that, the name is not enclosed in quotes like in your example. FYI, I am using the French version of Thunderbird and Lightning, would that make a difference?
Comment 4•10 years ago
|
||
This is one of the issues we should be looking into for 3.3.1, Thunderbird wants to fix autocomplete issues for their 31.1.0 too.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → 3.3.1
Assignee | ||
Comment 5•10 years ago
|
||
This one should take care.
Comment 6•10 years ago
|
||
Comment on attachment 8466800 [details] [diff] [review] SplitAddressListCorrectly-V1.diff Review of attachment 8466800 [details] [diff] [review]: ----------------------------------------------------------------- ::: calendar/base/content/dialogs/calendar-event-dialog-attendees.xml @@ +1055,5 @@ > if (element.value.contains(",")) { > let strippedAddresses = element.value.replace(/.* >> /, ""); > + let addresses = MailServices.headerParser.makeFromDisplayAddress(strippedAddresses); > + element.value = parseHeaderValue(addresses[0]); > + Some whitespaces snuck in here.
Attachment #8466800 -
Flags: review?(philipp) → review+
Assignee | ||
Comment 7•10 years ago
|
||
Updated patch with whitespaces removed.
Attachment #8466800 -
Attachment is obsolete: true
Assignee | ||
Updated•10 years ago
|
Keywords: checkin-needed
Assignee | ||
Comment 8•10 years ago
|
||
Do we want this also to be applied on aurora and beta beside release branch?
Flags: needinfo?(philipp)
Updated•10 years ago
|
Attachment #8468678 -
Flags: review+
Attachment #8468678 -
Flags: approval-calendar-release+
Attachment #8468678 -
Flags: approval-calendar-beta+
Attachment #8468678 -
Flags: approval-calendar-aurora+
Flags: needinfo?(philipp)
Comment 9•10 years ago
|
||
Pushing so this can get picked up by the release builds: https://hg.mozilla.org/releases/comm-esr31/rev/8317f9ef0d98
Comment 11•10 years ago
|
||
https://hg.mozilla.org/comm-central/rev/078e78571a92 https://hg.mozilla.org/releases/comm-aurora/rev/a032736616b7 https://hg.mozilla.org/releases/comm-beta/rev/fe7fc7bc40bf This patch will not be in 3.4, but given its not a major release and the cycle is long gone, I'm not going to fix it there.
You need to log in
before you can comment on or make changes to this bug.
Description
•