| Summary | HTML format breaks |
| Queue | IMP |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | scott (at) troutnet (dot) org |
| Created | 12/11/2012 (4586 days ago) |
| Due | |
| Updated | 12/13/2012 (4584 days ago) |
| Assigned | |
| Resolved | 12/13/2012 (4584 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
contemporary standard. You may ignore this bug but solving it should
be extremely simple. The spell-check-on-send feature just needs to
render the html content before spell checking, which would even work
in the example you provided. But if you and the rest of the Horde
staff prefer to market your product exclusively to users who use only
plain ASCII emails, I wish you luck. It's not 1992 anymore.
Actually, the spell check on send itself is a pretty stupid feature
since the advent of SCAYT (spell check as you type),which I have yet
to figure out how to enable in Horde. I'm feeling like I need to make
my own webmail client (lol?)
Cheers
conversations and the continuous back and forth replying, emails
quickly fill with a tremendous amount of junk.
replied message? That seems extremely un-useful.
First, you are going to be catching spell errors in the original
message (which are irrelevant). And its doubtful that all misspelled
words will be caught (and there will probably be false positives)
since it is pretty much impossible to determine discrete "words" in
HTML data. For example:
<span>t</span><span>e</span><span>e</span><span>s</span><span>t</span>. Boom:
there's a misspelled word (teest) that won't be caught.
You are right: this shouldn't be low priority, this should be zero
priority. In fact, thinking about this... we should probably totally
disable spellchecking for any HTML data NOT created via IMP. That's
the only way of guaranteeing some semblance of acceptable
spellchecking performance.
follow these steps:
1) Enable "Check spelling before sending a message" (under
Options->Preferences->Mail->Composition)
2) Select "Rich Text (HTML)" as the Default method to compose messages
(again under Options->Preferences->Mail->Composition)
3) Save
4) Compose a new message to yourself and send it.
5) Reply to the message just received - Send it to yourself.
6) View the message just received and note that there is HTML in the text
...for a more dramatic example
4 cont'd) follow steps 1-4 above, but when composing an original
message to yourself, click the "Source" button in CKeditor and enter
the following text:
foo <img src="http://h4x.us/x"> bar
5) Send the message, then reply to the message just received.
6) View the message just received and note that there is A LOT of
junk in the email.
This bug may seem a low priority but due to the nature of email
conversations and the continuous back and forth replying, emails
quickly fill with a tremendous amount of junk.
Thanks,
Scott
"Teesting" takes me to the spelling check - after correcting the
message, it is sent:
--=_krM1Ij5wUE2k-Q3jUZNTBg1
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
Content-Description: Plaintext Message
Content-Disposition: inline
Testing
--=_krM1Ij5wUE2k-Q3jUZNTBg1
Content-Type: text/html; charset=UTF-8
Content-Description: HTML Message
Content-Disposition: inline
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<!--a75c305b1c0a6022--><title></title>
</head>
<body style="font-family:Arial;font-size:14px">
<p>Testing</p>
</body>
</html>
--=_krM1Ij5wUE2k-Q3jUZNTBg1--
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ HTML format breaks
Due ⇒ 02/01/2013
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
selected), and worse turns the HTML into text which gets sent in the
email.