Re: Enable HTML email on the go
Paul B. Gallagher pau...@pbgdashtranslations.com wrote: Rob wrote: Paul B. Gallagher pau...@pbgdashtranslations.com wrote: Tihomir wrote: Normally, I do not use HTML in email. However, I sometimes need to insert graphic content like screenshots in my email. And it's much quicker to just paste screenshots into HTML mail than to save them first as files, then attach them. So, is there a way to switch between HTML and plain text quickly, without going to the preference screen in identity management? Once you've begun to compose a message, you're stuck with your decision (plain text/HTML). Options - Format in the message composition window lets you switch. Not available in my SM v. 2.14.1. Under Options, I have only: Select Addresses... Quote Message Return Receipt Delivery Status Notification Priority Character Encoding Send a Copy To Encrypt This Message Digitally Sign This Message You need to put the checkmark to compose messages in HTML in your account settings (under compose). What's slrn/pre1.0.0-18 (Linux)? That is a newsreader. It is unrelated to this discussion. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Nasty font tag bug in newish versions (maybe since 2.13)
I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. What makes it even worse is that stupid change (made a couple of versions before) to pretty-print the outgoing HTML. It is indented based on the tag level, so each level of font indents it more. There is absolutely no point in doing that, it only wastes space and bandwidth for no purpose. The combined result is HTML crap that even Microsoft would be ashamed of. I think some priority has to be given to fix both bugs. The pretty-printing should at least be made optional, defaulting to off, and the change that introduced the font size problem should be reverted or looked at. I had to disable font size preselection (by lockPref) temporarily to work around the issues it causes. But I know of no way to turn off the pretty-printing. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
Rob wrote: I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. What makes it even worse is that stupid change (made a couple of versions before) to pretty-print the outgoing HTML. It is indented based on the tag level, so each level of font indents it more. There is absolutely no point in doing that, it only wastes space and bandwidth for no purpose. The combined result is HTML crap that even Microsoft would be ashamed of. I think some priority has to be given to fix both bugs. The pretty-printing should at least be made optional, defaulting to off, and the change that introduced the font size problem should be reverted or looked at. I had to disable font size preselection (by lockPref) temporarily to work around the issues it causes. But I know of no way to turn off the pretty-printing. Is this what you're after? editor.prettyprint -- Ed Mullen http://edmullen.net/ UnHallmark Card: Happy birthday! You look great for your age. Almost Lifelike! ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
On 12/19/12 7:30 AM, Rob wrote: I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. What makes it even worse is that stupid change (made a couple of versions before) to pretty-print the outgoing HTML. It is indented based on the tag level, so each level of font indents it more. There is absolutely no point in doing that, it only wastes space and bandwidth for no purpose. The combined result is HTML crap that even Microsoft would be ashamed of. I think some priority has to be given to fix both bugs. The pretty-printing should at least be made optional, defaulting to off, and the change that introduced the font size problem should be reverted or looked at. I had to disable font size preselection (by lockPref) temporarily to work around the issues it causes. But I know of no way to turn off the pretty-printing. Have you submitted a bug report at bugzill.mozilla.org? If so, what is the bug number? -- David E. Ross http://www.rossde.com/ Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
On 12/19/2012 10:30 AM, Rob wrote: I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. Sounds related to this bug. https://bugzilla.mozilla.org/show_bug.cgi?id=756984 snip -- Fedora 17 (64-bit) KDE 4.9.2 Thunderbird Release Approximately 400 billion gallons of water are used worldwide per day. One inch of rain falling on one acre of land is equal to roughly 27,154 gallons of water. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Enable HTML email on the go
Rob wrote: You need to put the checkmark to compose messages in HTML in your account settings (under compose). That defeats the purpose if I don't use HTML most of the time. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: question about sessions, cookies, and permissions
Michael Ströder wrote: NFN Smith wrote: LMH wrote: Also, my cookie permissions seem to be disappearing. I use google as my home page. When I open my browser, I get a prompt to set a cookie. I select, allow for session, and check the use every time check box, but every time I open my browser I get the same prompt asking if that cookie can be set. I also get a cookie request from id.google.com. I set this to block and use every time, but I get that request ever time I open my browser as well. This one appears to be a problem in both Firefox 17 and Seamonkey 2.14. Upgrade to 2.14.1 fixed the cookie permission issues for me. Ciao, Michael. That's good to hear, hopefully this will go back to normal when I upgrade. LMH ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Enable HTML email on the go
Tihomir cdiamond...@yahoo.co.uk wrote: Rob wrote: You need to put the checkmark to compose messages in HTML in your account settings (under compose). That defeats the purpose if I don't use HTML most of the time. True. I use HTML by default and only switch to plain text mode when I know I am mailing to something like an abuse desk or similar, who still demand plain text. In the setup I have, Seamonkey will autodetect the situation, sending plain text when you only type plain text into the HTML composition window and using HTML once you do something that requires it, but I'm not sure which is the setting that does this. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
David E. Ross nobody@nowhere.invalid wrote: On 12/19/12 7:30 AM, Rob wrote: I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. What makes it even worse is that stupid change (made a couple of versions before) to pretty-print the outgoing HTML. It is indented based on the tag level, so each level of font indents it more. There is absolutely no point in doing that, it only wastes space and bandwidth for no purpose. The combined result is HTML crap that even Microsoft would be ashamed of. I think some priority has to be given to fix both bugs. The pretty-printing should at least be made optional, defaulting to off, and the change that introduced the font size problem should be reverted or looked at. I had to disable font size preselection (by lockPref) temporarily to work around the issues it causes. But I know of no way to turn off the pretty-printing. Have you submitted a bug report at bugzill.mozilla.org? If so, what is the bug number? I did not submit the report, the bug 812638 is the same thing but for Thunderbird. Unfortunately it looks like people want to replace the entire editor to fix this. That may take years. And what do we do in the meantime? (it worked OK one or two versions ago, it should be possible to fix it) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
WaltS wls15...@removeyahoo.com wrote: On 12/19/2012 10:30 AM, Rob wrote: I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. Sounds related to this bug. https://bugzilla.mozilla.org/show_bug.cgi?id=756984 No, that is something else. I think 812638 is closer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
On 12/19/2012 01:11 PM, Rob wrote: WaltS wls15...@removeyahoo.com wrote: On 12/19/2012 10:30 AM, Rob wrote: I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. Sounds related to this bug. https://bugzilla.mozilla.org/show_bug.cgi?id=756984 No, that is something else. I think 812638 is closer. You may be correct. Both are Core, Editor bugs. -- Fedora 17 (64-bit) KDE 4.9.2 Thunderbird Release Approximately 400 billion gallons of water are used worldwide per day. One inch of rain falling on one acre of land is equal to roughly 27,154 gallons of water. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
Ed Mullen e...@mungeedmullen.net wrote: Rob wrote: I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. What makes it even worse is that stupid change (made a couple of versions before) to pretty-print the outgoing HTML. It is indented based on the tag level, so each level of font indents it more. There is absolutely no point in doing that, it only wastes space and bandwidth for no purpose. The combined result is HTML crap that even Microsoft would be ashamed of. I think some priority has to be given to fix both bugs. The pretty-printing should at least be made optional, defaulting to off, and the change that introduced the font size problem should be reverted or looked at. I had to disable font size preselection (by lockPref) temporarily to work around the issues it causes. But I know of no way to turn off the pretty-printing. Is this what you're after? editor.prettyprint Yes something like that, but the above pref works in the editor (composer). I need a similar pref that affects the mail composition in the same way that the above pref affects the composer. (I remember I tested this before and now tested it again on 2.14.1 but it really only affects the composer) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
WaltS wls15...@removeyahoo.com wrote: On 12/19/2012 01:11 PM, Rob wrote: WaltS wls15...@removeyahoo.com wrote: On 12/19/2012 10:30 AM, Rob wrote: I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. Sounds related to this bug. https://bugzilla.mozilla.org/show_bug.cgi?id=756984 No, that is something else. I think 812638 is closer. You may be correct. Both are Core, Editor bugs. I hope it will be fixed quickly. Sometimes I hate the fact that we have to update because of security notices and then find that arbitrary changes have been made that introduce problems that never existed before (or have existed before and then been fixed). I understand that where there is development there always will be mistakes, but sometimes it looks like there is an ongoing train of development rushing forward without checking what blows off at the back. Fixing bugs introduced in a new version should be done before continuing into yet another new one. (I know I should join the development team instead of criticize, however while I have done a lot of C programming in the past this project is simply too large for me. I tried finding the location of a bug before, but even knowing what I was looking for I could not locate the sourcefile where the function that I was looking for was being performed...) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Set the remember password checkmark by default?
When a mail account is accessed, the program asks for a password and offers to remember this password. Is it possible (via some pref?) to make the remember password checkmark appear on by default? (so the user can still uncheck it) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Do NOT Install New Java Version 7u10 for Windows
It appears that Java 7u10 for Windows does not work for SeaMonkey 2.14.1. Both the Java installation test at http://www.java.com/en/download/installed.jsp and a known Web site that uses Java fail when that version is installed; they indicate that there is no Java plugin. Running the test and visiting the other site after removing Java 7u10 and reinstalling Java 7u9 work okay. This has been reported to Oracle. -- David E. Ross http://www.rossde.com/ Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Set the remember password checkmark by default?
On 12/19/12 11:49 AM, Rob wrote: When a mail account is accessed, the program asks for a password and offers to remember this password. Is it possible (via some pref?) to make the remember password checkmark appear on by default? (so the user can still uncheck it) Remembering your password in SeaMonkey -- even when encrypted by your master password -- will always remain at least slightly less secure than remembering your password in your head. Thus the default is not to remember it in SeaMonkey. -- David E. Ross http://www.rossde.com/ Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
On 12/19/12 10:53 AM, Rob wrote: WaltS wls15...@removeyahoo.com wrote: On 12/19/2012 01:11 PM, Rob wrote: WaltS wls15...@removeyahoo.com wrote: On 12/19/2012 10:30 AM, Rob wrote: I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. Sounds related to this bug. https://bugzilla.mozilla.org/show_bug.cgi?id=756984 No, that is something else. I think 812638 is closer. You may be correct. Both are Core, Editor bugs. I hope it will be fixed quickly. Sometimes I hate the fact that we have to update because of security notices and then find that arbitrary changes have been made that introduce problems that never existed before (or have existed before and then been fixed). I understand that where there is development there always will be mistakes, but sometimes it looks like there is an ongoing train of development rushing forward without checking what blows off at the back. Fixing bugs introduced in a new version should be done before continuing into yet another new one. (I know I should join the development team instead of criticize, however while I have done a lot of C programming in the past this project is simply too large for me. I tried finding the location of a bug before, but even knowing what I was looking for I could not locate the sourcefile where the function that I was looking for was being performed...) However, the problem is easily resolved by composing only ASCII-formatted messages. -- David E. Ross http://www.rossde.com/ Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
David E. Ross nobody@nowhere.invalid wrote: However, the problem is easily resolved by composing only ASCII-formatted messages. This is not realistic in today's world when using the program in a company. Most mail being processed is in HTML. We even have HTML signatures. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Do NOT Install New Java Version 7u10 for Windows
David E. Ross nobody@nowhere.invalid wrote: It appears that Java 7u10 for Windows does not work for SeaMonkey 2.14.1. Both the Java installation test at http://www.java.com/en/download/installed.jsp and a known Web site that uses Java fail when that version is installed; they indicate that there is no Java plugin. Running the test and visiting the other site after removing Java 7u10 and reinstalling Java 7u9 work okay. This has been reported to Oracle. Thanks for telling us, saves me the effort and problems of deploying the Java update just now. Did you check the new items in the control panel to see if the new security settings for enabling Java in the browser come up correctly? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Set the remember password checkmark by default?
David E. Ross nobody@nowhere.invalid wrote: On 12/19/12 11:49 AM, Rob wrote: When a mail account is accessed, the program asks for a password and offers to remember this password. Is it possible (via some pref?) to make the remember password checkmark appear on by default? (so the user can still uncheck it) Remembering your password in SeaMonkey -- even when encrypted by your master password -- will always remain at least slightly less secure than remembering your password in your head. Thus the default is not to remember it in SeaMonkey. Many defaults are settable by pref in Seamonkey, only it is not always easy to find the name of the pref. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Do NOT Install New Java Version 7u10 for Windows
David E. Ross wrote: It appears that Java 7u10 for Windows does not work for SeaMonkey 2.14.1. Both the Java installation test at http://www.java.com/en/download/installed.jsp and a known Web site that uses Java fail when that version is installed; they indicate that there is no Java plugin. Running the test and visiting the other site after removing Java 7u10 and reinstalling Java 7u9 work okay. This has been reported to Oracle. My mileage varies. My standard test for Java is http://www.chessgames.com/ and that works fine, your www.java.com link shows You have the recommended Java installed (Version 7 Update 10).. Win XP ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Do NOT Install New Java Version 7u10 for Windows
David E. Ross wrote: It appears that Java 7u10 for Windows does not work for SeaMonkey 2.14.1. Both the Java installation test at http://www.java.com/en/download/installed.jsp and a known Web site that uses Java fail when that version is installed; they indicate that there is no Java plugin. Running the test and visiting the other site after removing Java 7u10 and reinstalling Java 7u9 work okay. This has been reported to Oracle. I thought that perhaps I might have the same problem (as it worked fine in Firefox - Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20100101 Firefox/17.0), But not SeaMonkey. However, after closing and restarting SeaMonkey again, Java7u10 is working for me: Java(TM) Platform SE 7 U10 File: npjp2.dll Version: 10.10.2.18 Next Generation Java Plug-in 10.10.2 for Mozilla browsers User agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20100101 Firefox/17.0 SeaMonkey/2.14.1 Build identifier: 20121129191119 http://java.com/en/download/installed.jsp Verified Java Version Completion checkmark Congratulations! You have the recommended Java installed (Version 7 Update 10). Try from Firefox see if that works for you. If it works there, but not in SeaMonkey, then try a test profile. Note: This WinXP SP3 is running in a virtual machine (VMWare). To turn Java on/off I am using Prefbar 6.2.0. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
Rob wrote: David E. Ross nobody@nowhere.invalid wrote: However, the problem is easily resolved by composing only ASCII-formatted messages. This is not realistic in today's world when using the program in a company. Most mail being processed is in HTML. We even have HTML signatures. Amen. The last job I had was in 1996 and ALL email was HTML. Where are you text-only people coming from? -- Ed Mullen http://edmullen.net/ Harmony of aim, not identity of conclusion, is the secret of sympathetic life. - Ralph Waldo Emerson ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
2.14.1 mouse cursor changes to drag drop
In the past few days I've noticed my mouse cursor changing to 'DD' anytime that I move the mouse over a tab quickly. Similar to the issue of: https://bugzilla.mozilla.org/show_bug.cgi?id=736811 [Mouse occasionally changes to drag cursor and the mouse buttons stop functioning] Except in my case the mouse buttons et al continue to work fine. Anyone else noticing the same? User agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20100101 Firefox/17.0 SeaMonkey/2.14.1 Build identifier: 20121129191050 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Resolved? [was: Do NOT Install New Java Version 7u10 for Windows]
On 12/19/12 11:55 AM, David E. Ross wrote: It appears that Java 7u10 for Windows does not work for SeaMonkey 2.14.1. Both the Java installation test at http://www.java.com/en/download/installed.jsp and a known Web site that uses Java fail when that version is installed; they indicate that there is no Java plugin. Running the test and visiting the other site after removing Java 7u10 and reinstalling Java 7u9 work okay. This has been reported to Oracle. It appears that installing Java 7u10 failed to remove completely Java 7u9. A process of the earlier version remained running in the background, blocking the removal of a .dll file it used. First I used Unlocker to unlock the .dll file so that I could manually delete it, but that failed. I then used Unlocker kill the remnant Java process that was locking the file. SUCCESS!! (I hope.) -- David E. Ross http://www.rossde.com/ Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Nasty font tag bug in newish versions (maybe since 2.13)
On 19/12/2012 23:30, Rob wrote: I found by accident that the 2.14.1 version we are using now has a nasty bug in the message composition mode. When composing in HTML, and after setting a custom font size in the options for message composition (default is medium, set to small or large for example) the composer peppers a lot of nested font size=x /font tags in the message. Many more than are required. It is not clear to me when it inserts a new one, maybe after backspacing or similar. I saw messages with 20 or more nested font tags. What makes it even worse is that stupid change (made a couple of versions before) to pretty-print the outgoing HTML. It is indented based on the tag level, so each level of font indents it more. There is absolutely no point in doing that, it only wastes space and bandwidth for no purpose. The combined result is HTML crap that even Microsoft would be ashamed of. I think some priority has to be given to fix both bugs. The pretty-printing should at least be made optional, defaulting to off, and the change that introduced the font size problem should be reverted or looked at. I had to disable font size preselection (by lockPref) temporarily to work around the issues it causes. But I know of no way to turn off the pretty-printing. https://bugzilla.mozilla.org/show_bug.cgi?id=812638 Bug 812638 - Thunderbird is inserting random and incorrect font size=3 tags in the middle of words throughout my email message. (edit) Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
