Daniel wrote on 25/03/15 16:53:
On 25/03/15 09:20, mozilla-lists.mbou...@spamgourmet.com wrote:
Ant wrote:
Well, that is interesting. I usually send plain text anyway, and only
occasionally send HTML, so may not have noticed a change. Just tried a
couple of experiments:
1. Start a message in HTML format (shift+click compose, since I
have it
default to plain text), type a short message but don't actually apply
any formatting and click send. It sends as plain text without
prompting.
OK, sounds like mine.
2. Start a message in HTML format, type a message, colour one word red
and click send. It prompts for whether to send as plain text, HTML or
both.
So it looks like it automatically sends as plain text if you don't
make
any use of HTML formatting. Does that match your experience? Or is it
discarding formatting even if you have applied some?
The only thing I changed was the formatting like centering a
section/paragraph. Now, I see the issue now. If I don't change colors,
bold or anything like that, then it goes back to plain text! Why can't
formatting a paragraph/section keep it as HTML?
I can confirm that - setting some paragraphs left, centred, right or
justified (even mixing all of these in a single email) but not applying
any other formatting leads to the message being sent as plain text
without prompting.
Is this a bug?
It's not really my call any more than yours, but I'd say it is.
My guess is that someone complained about the prompt saying "you used
formatting (e.g. colours)..." even if no formatting has been applied,
and the solution was to detect whether any formatting has been applied
and just send as plain text if not. Looks like that's a bit flawed
though, in not checking for paragraph alignment formatting!
Are you familiar with Bugzilla (https://bugzilla.mozilla.org/)? It's not
that difficult once you know your way around. The main complication is
that SeaMonkey isn't on the main page for reporting a new issue - you
have to go to File a Bug > Other Products > SeaMonkey, then it's fairly
straightforward. Post back if you get stuck and I'll be happy to help.
In fact, it would be useful if you could post back anyway with the bug
number, so anyone else coming across this thread knows about it.
As for a workaround until its fixed - perhaps just add a space at the
end and make it bold or something. You can do that in a signature to
avoid having to remember every time - Edit > Account Settings > (Select
Account) > Tick "Use HTML" next to "Signature text", and in the box just
below enter or add to any existing signature "<font color="red">
</font>" (there's a space in the middle between ">" and "<"). It's not
perfect, as it inserts a signature delimiter (-- ) if you weren't using
a signature anyway, but at least the alignment isn't lost.
Mark.
Speaking about HTML and sig delimiters, there was a problem of the sig
delimiter being with-in the HTML, so, when that post/e-mail was
quoted, the sig was not getting removed.
Has that problem been fixed yet??
In tonight's nightly trunk build for "Edit as New" and "Forward", the
sig. is being included as normal-text , but it's completely-removed for
"Reply to Sender" in HTML bodies.
Signature delimitation sure has thrown up a lot of open bugs that affect
the composing behaviour:-
<https://bugzilla.mozilla.org/buglist.cgi?quicksearch=mail+signature>
We now have account-signature Preferences for both 'reply' and
'forward' in "Edit, Mail & Newsgroup Account Settings, mail or newsgroup
account-name, Composition and Addressing, Composition", which is a step
towards users choosing where they enforce the signature delimiter.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
