Closed
Bug 695470
Opened 14 years ago
Closed 10 years ago
editing message containing mail address does not update mailto link
Categories
(SeaMonkey :: MailNews: Composition, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: bugzilla, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110923 Firefox/7.0 SeaMonkey/2.4
Build ID: 20110923021706
Steps to reproduce:
Edit a mail message that has been "linkified" before, e.g. a reply, forward, edit as new.
Actual results:
Linkified e-mail address, when edited, changes only the displayed address and not the address in the mailto: link.
Expected results:
When the displayed mail address in a mailto: link is edited, and the mailto: before the edit is the same as the displayed address, edit the link as well.
When an e-mail address is entered in a (HTML) mail message, it is automatically linkified to something like: <a href="mailto:user@example.com">user@example.com</a>
When this message is received and again edited, it shows up as a blue underlined user@example.com
Now, when the user edits this blue text, e.g. to info@example.com, the result in the sent mail is like: <a href="mailto:user@example.com>info@example.com</a> i.e. the address as seen by the reader is changed, but when clicking on the link a mail to the old address is being composed.
This is quite confusing.
| Reporter | ||
Updated•14 years ago
|
Component: General → MailNews: Composition
OS: Linux → All
Hardware: x86_64 → All
Comment 1•11 years ago
|
||
I haven't a clue what the problem might be, and it seems that HTML mail composition is completely broken in ma SeaMonkey?
When I create a HTML mail with a mailto-link, souce code looks as expected and described in original report.
But after having sent that mail to several of my email accounts, the html source code always will have gone and be replaced by a text line like
<RainerBielefeldNG@BielefeldUndBuss.de <mailto:RainerBielefeldNG@BielefeldUndBuss.de>>
So currently I do not have a chance to test this one.
@Reporter:
can you confirm my observation that mailto: hyperlinks are compeletly borken in HTML emails?
Flags: needinfo?(pe1chl)
| Reporter | ||
Comment 2•11 years ago
|
||
Nothing has changed. The bug is still there. I don't see the problem you are reporting.
Comment 3•11 years ago
|
||
(In reply to Rob Janssen from comment #2)
I see [Bug 780365] during sending: Mailto Link in Content-Type: text/html; charset=UTF-8 becomes duplicated e-mail-address in Content-Type: text/plain; charset=UTF-8; format=flowed
Comment 4•10 years ago
|
||
NOT reproducible with English SeaMonkey 2.47a1 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build 20160712003002 (Default Classic Theme) on VirtualBox Ubuntu 12.04 LTS
0. For 2 used Email accounts select preference "compose as HTML"
1. Compose HTML-Mail with message body
"sended mobil_info@receiver.de to me " → Send to
mobil_info@receiver.de
2. view mail in "Sent" folder, move mouse pointer to email address in body:
» correctly shows "mobil_info@receiver.de" in Status Bar
3. view mail in "Inbox" folder, move mouse pointer to email address in body:
» correctly shows "mobil_info@receiver.de" in Status Bar
4. In Inbox select received email, click 'Reply' icon
» Composer Window opens, shows HTML email
5. in quote modify "mobil_info@receiver.de" to
"info@receiver.de" → Send to info@receiver.de
6. In received email in Inbox move mouse pointer to "info@receiver.de"
in Inbox:
» correctly shows "info@receiver.de" in Status Bar
So WFM for now.
@Reporter: Please feel free to reopen this Bug if you still can reproduce the problem with a current SeaMonkey version and a current OS and if you can contribute a step by step instruction how to reproduce the problem due to <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines> (containing every key press and every mouse click) how to reproduce the problem reliably.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
OS: All → Linux
Resolution: --- → WORKSFORME
| Reporter | ||
Updated•7 years ago
|
Flags: needinfo?(pe1chl)
You need to log in
before you can comment on or make changes to this bug.
Description
•