Closed Bug 73551 Opened 24 years ago Closed 24 years ago

js warnings in msgMail3PaneWindow.js and msgViewNavigation.js

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: sspitzer, Assigned: sspitzer)

Details

Attachments

(1 file)

these are probably covered in other bugs, but I need a place to attach my patch.
here comes a patch
Status: NEW → ASSIGNED
Summary: js warnings → js warnings in msgMail3PaneWindow.js and msgViewNavigation.js
It's kind of hard to review this bug w/o the errors reported. Why are you removing the 'outlinerview' variable? That is used a few lines below.
Summary: js warnings in msgMail3PaneWindow.js and msgViewNavigation.js → js warnings in msgMail3PaneWindow.jsand msgViewNavigation.js
hwaara, the variable is defined and assigned a few lines up. I'll provide the js warnings this afternoon.
Summary: js warnings in msgMail3PaneWindow.jsand msgViewNavigation.js → js warnings in msgMail3PaneWindow.js and msgViewNavigation.js
Ah, I checked LXR and now I see. r=hwaara
here are the warnings: JavaScript strict warning: chrome://messenger/content/msgViewNavigation.js line 107: function CrossFolderNavigation does not always return a value JavaScript strict warning: chrome://messenger/content/msgViewNavigation.js line 171: function CrossFolderNavigation does not always return a value WARNING: waaah!, file nsXULPrototypeDocument.cpp, line 523 JavaScript strict warning: chrome://messenger/content/msgMail3PaneWindow.js line 206: redeclaration of var outlinerView
fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Using 2001-04-04 on windows and ran app with 3-pane window, navigating to Next folder with next Unread button while console was up and did not see the js warnings. Verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: