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
