I'm going to attach a message to this bug which looks bad in mozilla in two interesting ways: 1. It looses a bunch of the CR/LFs when we display it. The '>' lines get jumbled together, and blank lines get removed. 2. It uses the variable width font, which seems wrong since the message is not format=flowed. It was sent by NS 4.7.

Nominate for nsbeta2

My build from 2000-04-11 with my heavy changes for bug 31906 doesn't show the bug. I do see it in a nightly from 2000-04-22. Maybe, somebody with a good net connection to ftp.mozilla.org can d/l the 2000-04-11 nightly to make sure, I didn't "accidently" fixed it with my changes, but it is a regression? If yes, it is most likely caused by nhotta. REASSIGNing to him.

I see this problem on all builds using the following builds: win32 commercial seamonkey build 00042609-m16 installed on Dell P500, Win98 macos mozilla seamonkey build 00042611-m16 installed on G3/400, MacOS 9 linux commercial seamonkey build 00042608-m16 installed on P200, RedHat 6.1 If I view the same message in 4.7/4.72, the messages displays fine. It did not matter if I viewed the message under IMAP or POP. I took a screen shot on what it look like on 4.7 vs. 5.0 that I will post.

Putting on [nsbeta2+] radar.

Accepting, this is a side effect of my font setting change bug 26182.

Fix checked in, changed to use <pre> instead of <div> for plain text cases.

nhotta, what was the problem and why fixed this it? There already is a <pre> at line <http://lxr.mozilla.org/seamonkey/source/mailnews/mime/src/mimetpla.cpp#133>. I don't know, why it isn't used in some cases (still don't understand which cases - some plain text msgs worked). I should know, because all this will change with my fix for bug 31906 (see above). Thanks.

My change was to set a default font so the layout won't pick up the unicode font (since the output sent to the layout is UTF-8). I place the tag before other existing tags so it was not supposed to affect inner tags. Somehow <br> affected the inside <pre> you generated. I don't know why this happened but changed to <pre> enabled your tag again. BTW, as you mentioned in the bug 26182, the default font setting is ignored in case of format=fixed because your tag overrides it. Is that possible for you to used the default font name and size in your tag if I provide those info? Then I don't have to place the extra tag.

Just installed the 4/28 build, and this bug is not fixed. Reopening.

On my machine, the view of the message using PR1 and 4/28 build are the same (win32 builds). I will attach a screen shot.

I too still see the problem under IMAP and POP on win32, macos, and linux using today release builds 2000-042809-m16. Before running todays build, I threw away my previous profile and started fresh. The problem is still there for me. Sorry, I can't verify this bug.

Peter, you attached two screen shots. Why they're different are both views incorrect? On my machine, when using the variable font option I get the same view as the first screen shot (04/26/00 16:43) both PR1 and 4/28 win32 builds.

On my machine, I see the same thing as the 4/26 16:44 screen shot. I'm using the 2000042809 build on NT.

I see the problem after I create a new profile (probably something special in my prefs.js).

Thank you nhotta. I'm glad you were able to reproduce the problem. :)

Okay, there was one place I missed the change last time. I will check in on Monday.

fix checked in

Peter, can you verify this one now that ab feature you were testing is not immediate on our testing? Thanks

Verified as fixed on branch builds of win32, linux, and macos. Win32 commercial seamonkey build 2000-080205-m17 Linux commercial seamonkey build 2000-080204-m17 Macos commercial seamonkey build 2000-080204-m17