Closed
Bug 258477
Opened 20 years ago
Closed 20 years ago
add to address book through from line does not read vcard data
Categories
(SeaMonkey :: MailNews: Address Book & Contacts, defect)
SeaMonkey
MailNews: Address Book & Contacts
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: mh519, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-gb; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Thunderbird 0.7.3 (20040803)
(For emails including vCards)
If you add someone to your address book using the context menu of the from line,
data from the vCard is not imported into the add new card dialog. Instead you
must use the vCard icon, which is not always visible on longer emails.
Reproducible: Always
Steps to Reproduce:
1. Receive an email containing a vCard
2. Add the sender to your address book through the context menu
Actual Results:
Data in new card dialog will not include anything from their vCard, only the
display name and email.
Expected Results:
Data from vCard, such as address and tel will have been read and appear in the
new card dialog.
Summary: add to address book does not read vcard data → add to address book through from line does not read vcard data
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Comment 1•20 years ago
|
||
Sorry, I'm resolving this one as invalid - a vcard is a seperate attachment to a
mail, it may not even be the vcard of the sender from whom you got the email.
When you add the sender from the context menu on the "from" line, you are just
adding the sender's detail - there is no link to the vcard. You could possibly
argue we could try and link the email addresses or names but I don't think thats
the right way to go - and that would be a seperate bug anyway.
If you are having trouble with seeing the vcard icon on large emails, please
file a seperate bug after first having checked the latest release or nightly build.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•