Closed
Bug 837255
Opened 11 years ago
Closed 6 years ago
[B2G] [Leo][SMS]Sending email to contact shows display name in email as "foo@bar.com <foo@bar.com >"
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect, P2)
Tracking
(tracking-b2g:backlog, b2g18?, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected)
RESOLVED
WONTFIX
tracking-b2g | backlog |
People
(Reporter: cjones, Assigned: arcturus)
References
Details
(Whiteboard: permafail)
Attachments
(1 file)
STR (1) Add a contact "John Smith" with address foo@bar.com (2) Open contact in details view (3) Tap to send an email I expect the "To:" line to show up as "John Smith <foo@bar.com>", but instead it shows up as "foo@bar.com <foo@bar.com>". Not sure which app is at fault here. b? -> radar
email is if I'm reading the code right : https://github.com/mozilla-b2g/gaia/blob/v1.0.0/apps/email/js/compose-cards.js#L106
Comment 2•11 years ago
|
||
The easier solution for this issue is passing the name from contact, and email can receive both email address and name. Another solution is implementing the contact management(helper function set for contact related stuff like auto-complete) in email. I think it's necessary to have this feature eventually, but we can apply the former solution quickly or just implement part of the contact management if this issue is urgent. Thanks.
Comment 3•11 years ago
|
||
Not a blocker, but tracking - user is still able to email and shouldn't be confused by this. Mostly cosmetic.
blocking-b2g: tef? → -
tracking-b2g18:
--- → +
Comment 4•11 years ago
|
||
Steve - are you the right person to look into this for v1.x?
Assignee: nobody → schung
Comment 5•11 years ago
|
||
I can take a look after finishing TEF_REQ UX issue, thanks.
blocking-b2g: - → tef?
tracking-b2g18:
+ → ---
Comment 6•11 years ago
|
||
Er.. Sorry for flag reset
blocking-b2g: tef? → ---
tracking-firefox18:
--- → ?
Updated•11 years ago
|
tracking-b2g18:
--- → ?
tracking-firefox18:
? → ---
Reporter | ||
Updated•11 years ago
|
blocking-b2g: --- → -
Comment 7•11 years ago
|
||
Steve, are you working on this? I can take it if needed.
Flags: needinfo?(schung)
Comment 8•11 years ago
|
||
Almost 10 days without news so I'm going to steal the bug :)
Flags: needinfo?(schung)
QA Contact: isabelrios → alberto.pastor
Updated•11 years ago
|
Assignee: schung → alberto.pastor
QA Contact: alberto.pastor
Updated•11 years ago
|
QA Contact: isabelrios
Comment 9•11 years ago
|
||
Pointer to Github pull-request
Updated•11 years ago
|
Attachment #740811 -
Flags: review?(bugmail)
Comment 10•11 years ago
|
||
Comment on attachment 740811 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/9356 Rather than introducing an ad hoc e-mail address parser in the e-mail front-end, we should use the existing addressparser library, probably just in the back-end on the worker thread, but we could also do it in the back-end provided MailAPI on the main thread too. I've filed bug 864990 for that. Also, the e-mail address you are composing on the contacts side of the house is using obsolete syntax and could benefit from webspace. See https://tools.ietf.org/html/rfc2822#section-3.4 for more details, but you'd basically want to put the name in quotes (and probably just strip any quote characters that exist inside the name string), have a space character after the quotes. But we could also just avoid the need to pass everything through a mailto URI. I'd have no problem if our "new" verb for { type: "mail" } took a dict like { to: [ { name, address } ], cc: [], bcc: [], subject: "" }, and it would save everyone a lot of hassle that doesn't need to speak 'mailto' because they are real web things.
Attachment #740811 -
Flags: review?(bugmail) → review-
Comment 11•11 years ago
|
||
And s/webspace/whitespace. The string you create right now will look like: John Doe<john@example.doe> It should looke like: "John Doe" <john@example.doe>
Updated•11 years ago
|
Assignee: alberto.pastor → nobody
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → francisco.jordano
Comment 12•11 years ago
|
||
This issue tested on Leo 1.1 (Test Run Firefox OS 1.1.0 Full – Leo) Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/8e3f39363c54 Gaia: ea18de80fd04110756becaed214656642388401d Platform Version: 18.0 STEPS: 1.Send a sms from "device A" (DUT) to "device B" that contains an email address (e.g.: "tururut@gmail.com" which belongs to an existing contact (e.g.:"Lucy"), with two email address added 2.Open the SMS thread view in the device A (DUT) 3.Click on the email address ("tururut@gmail.com") EXPECTED RESULT: Email app is launched with the contact name ("Lucy")charged in "to:" field ACTUAL RESULT: Email app is launched only with the email address ("tururut@gmail.com")charged in "to:" field Link to failed test case: https://moztrap.mozilla.org/manage/case/7160/
Summary: Sending email to contact shows display name in email as "foo@bar.com <foo@bar.com>" → [B2G] [Leo][SMS]Sending email to contact shows display name in email as "foo@bar.com <foo@bar.com>"
Whiteboard: leorun3
Comment 13•11 years ago
|
||
Link to failed test case: https://moztrap.mozilla.org/manage/case/7161/ https://moztrap.mozilla.org/manage/case/7162/ https://moztrap.mozilla.org/manage/case/7163/
Comment 14•11 years ago
|
||
The e-mail app is now a lot more aggressive about mapping e-mail addresses to contacts (in the reader) and keeping them up to date, and we have been normalizing our 'peep bubble' representation in the UI. As such, it might make sense to kick the bug over to just being the e-mail app's problem and having the contacts app just provide the e-mail address since we'll resolve the e-mail address to a contact anyways. I filed bug 883008 about fixing that bit of e-mail.
Comment 15•11 years ago
|
||
Issue repros on Leo Build ID: 20130625070217 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/29933d1937db Gaia: 1436e2778b90bd74635b0b94d1cf8ccb0d71b60c Platform Version: 18.1 When sending a email to a address that is already in your contacts it shows as the email address and not the users name.
Comment 16•11 years ago
|
||
This issue tested on Leo 1.1 (Test Run Firefox OS 1.1.0 Full – Leo Run 4) Gecko a378807ff04076c20f08b0102286b9eb2d08d60a Gaia 1436e2778b90bd74635b0b94d1cf8ccb0d71b60c Platform Version: 18.1 STEPS: 1.Send a sms from "device A" (DUT) to "device B" that contains an email address (e.g.: "tururut@gmail.com" which belongs to an existing contact (e.g.:"Lucy"), with two email address added 2.Open the SMS thread view in the device A (DUT) 3.Click on the email address ("tururut@gmail.com") EXPECTED RESULT: Email app is launched with the contact name ("Lucy")charged in "to:" field ACTUAL RESULT: Email app is launched only with the email address ("tururut@gmail.com")charged in "to:" field Link to failed test case: https://moztrap.mozilla.org/manage/case/7160/ https://moztrap.mozilla.org/manage/case/7161/ https://moztrap.mozilla.org/manage/case/7162/ https://moztrap.mozilla.org/manage/case/7163/
Whiteboard: leorun3 → leorun3, leorun4
Updated•11 years ago
|
Whiteboard: leorun3, leorun4 → leorun3, leorun4, retest_leorun4
Updated•11 years ago
|
blocking-b2g: - → koi?
Updated•11 years ago
|
Blocks: comms_backlog
blocking-b2g: koi? → ---
Updated•11 years ago
|
Whiteboard: leorun3, leorun4, retest_leorun4 → leorun3, leorun4, retest_leorun4, burirun2
Updated•11 years ago
|
Whiteboard: leorun3, leorun4, retest_leorun4, burirun2 → leorun3, leorun4, retest_leorun4, burirun2, burirun3
Updated•11 years ago
|
Whiteboard: leorun3, leorun4, retest_leorun4, burirun2, burirun3 → permafail
Updated•10 years ago
|
status-b2g-v1.4:
--- → verified disabled
Updated•10 years ago
|
Updated•10 years ago
|
blocking-b2g: --- → backlog
Updated•10 years ago
|
status-b2g-v2.0:
--- → affected
Updated•10 years ago
|
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Updated•9 years ago
|
Priority: -- → P2
Comment 17•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•