Closed Bug 14115 Opened 26 years ago Closed 25 years ago

Inability To Scroll OE5 Messages In Mail Viewer Windows

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

Product:
SeaMonkey
Component:
MailNews: Message Display
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: BenB, Assigned: rhp)

Details

Newsgroups: netscape.public.mozilla.mail-news Message-ID: <7rrjqe$fdj3@secnews.netscape.com> Subject: Netscape Messenger Bug - Inability To Scroll Mail Messages In Mail Viewer Windows Date: Thu, 16 Sep 1999 16:26:57 -0400
From: "Frank T. Domina" <frank.domina@sciatl.com> Verbose copy: All, There is a bug in Netscape Messenger that Microsoft Outlook seems to exploit. The bug causes you to not be able to scroll messages that are longer than the visible window. This is only true in while VIEWING a message. In other words, it is a problem w/ Netscape's VIEWER. If you select reply or forward and bring up the e-mail in Netscape's editor, you can then scroll down to see everything. There's also another solution...read on... Ironically, it is Netscape's EDITOR that triggers the problem in their own VIEWER. Here's what happens: 1.Outlook inserts a style tag within the header section, something like: <head> <style></style> </head> 2.Netscape's VIEWER is completely happy with that. In fact, if you're looking at this message in Netscape right now, you can click on view page source and see that this message is formatted like that. 3.Here is where the problem comes in...If someone running Netscape replies or forwards the message, causing it to be pulled into Netscape's EDITOR, it's editor doesn't know what do do with that style tag. It actually causes a couple problems. It concatonates all lines together into one big line without spaces which causes a big ugly mess when later viewed by anyone that is running a mail client that doesn't support HTML (the plain-text version is really ugly) or if you have Netscape send the mail as plain-text only. It places the tag outside of the header (actually, Netscape eliminates the <head> and </head> tags altogether) which later causes problems by Netscape's mail viewer. 4.When Netscape's VIEWER sees the <style></style> tags which are no longer within the <head></head> tags (which it's own editor did to the message), it gets confused and chokes, disallowing you to scroll the message -- BUT -- when you reply/forward the message, Netscape's EDITOR doesn't mind the tags, doesn't get confused, and lets you scroll the message. 5.No matter what the location of the <style></style> tags, Outlook is perfectly happy, so us Outlook users don't even know there's a problem with the message that is causing Netscape users to have problems. What to do about it... The obvious work-around is that if you get a message that you can't scroll, reply/foward it to pull it into the editor and you'll be able to read it just fine. If you are a Netscape user, to PREVENT the problem, if you ever reply/forward a message and you see a little yellow tag icon in your mail, usually near the top of what the previous person sent to you, click on that tag icon and delete it. This eliminates the offending tag and the receivers of your mail will be able to see it just fine in Netscape's viewer. A simple, but annoying thing to have to do. If you are a Netscape user and want to verify what I'm saying, "forward as quoted" this message to yourself and you won't be able to scroll the message you receive from yourself (unless you delete the tag I mentioned). Also, if you go into your "sent" folder and try to look at the message, you will see it's messed up in there. I'm going to post this message to Netscape newsgroups in hope that the bug will eventually get fixed. FYI, the version of Outlook I'm using is Express 5.0. All versions of Netscape I've tried through 4.61 have this problem. Regards, Frank T. Domina =============== Sr. Staff Software Engineer Scientific-Atlanta, Inc. http://www.sciatl.com
Severity: normal → minor
As DavidMc said: "Forget MS", but I wonder, why Moz cares. Additional/unknown tags should neither irritate in (only wellformed) XML, HTML nor plain text. Marking minor.
Assignee: phil → rhp
Rich, not sure if this is really a MIME bug, per se, but could you take a look.
QA Contact: lchiang → pmock
changing QA assigned to pmock
Status: NEW → ASSIGNED
Target Milestone: M12
Seems bad...but won't be able to fix before midnight. - rhp
Target Milestone: M12 → M13
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
I've tested against OE messages that used to cause all sorts of display problems, and now everything is fine. Layout is in a much better place today than when these bugs were originally filed. Please let me know if you still see a problem. If you do, please post the contents of the message/rfc822 message for me to diagnose. - rhp
Verified as worksforme on win32, macos, and linux using the following builds: win32 commercial seamonkey build 00051109-m16 installed on Dell P500, Win98 macos commercial seamonkey build 00051008-m16 installed on G3/400, MacOS 9.04 linux commercial seamonkey build 00051008-m16 installed on P200, RedHat 6.1 I was not able to reproduce problem.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.