60736 - javascript strict warnings in contentAreaUtils.js

Status: VERIFIED WORKSFORME

(SeaMonkey :: UI Design, defect, P3)

Description

[Henrik Gemal]

JavaScript strict warning:
chrome://communicator/content/contentAreaUtils.js line 133: assignment to 
undeclared variable charsetArg

Comment 1

[Henrik Gemal]

Attachment: Patch to fix javascript strict warnings

Comment 2

[Viswanath Ramachandran]

Since Don has left, Vishy is taking his bugs in bulk, pending reassignment.
thanks,
	Vishy

Comment 3

[Paul Chen]

nav triage team:

Ok, there's a patch, let's get this in, marking nsbeta1, mozilla0.9, reassigning 
to pchen

Comment 4

[Blake Ross]

r=blake, cc alec for sr

Comment 5

[Alec Flett]

sr=alecf

Comment 6

[Blake Ross]

Fix checked in.

Comment 7

[Mark Olson]

Verified Linux 20010106

Comment 8

[Henrik Gemal]

In todays build:

JavaScript strict warning:
chrome://communicator/content/contentAreaUtils.js line 30: reference to
undefined property _content.frames

JavaScript error:
chrome://communicator/content/contentAreaUtils.js line 31: contentFrames has no
properties

Comment 9

[Paul Chen]

Henrik, do you still see this warning?

Comment 10

[Henrik Gemal]

kind of. Now it's an error...

JavaScript error:
chrome://communicator/content/contentAreaUtils.js line 31: contentFrames has no
properties

There seems to be some relationship between this bug and:
http://bugzilla.mozilla.org/show_bug.cgi?id=67623

Comment 11

[Paul Chen]

This has fallen off my mozilla0.9 list, marking nsbeta1-. It's not that I don't
want it fixed, but it's getting to that time where we gotta cut stuff.

Comment 12

[Paul Chen]

Marking nsbeta1+, mozilla0.9

Comment 13

[Paul Chen]

Moving to mozilla0.9.1

Comment 14

[Viswanath Ramachandran]

as discussed in team meeting, moving all Nav+ team members nsbeta1+ P3 bugs from 
mozilla0.9.1 to mozilla0.9.2. 

Comment 15

[Paul Chen]

nav triage team:

Pushing out to mozilla0.9.3

Comment 16

[Henrik Gemal]

Warning: reference to undefined property entry.postData
Source File: chrome://communicator/content/contentAreaUtils.js
Line: 86

Comment 17

[Paul Chen]

nav triage team:

Not a mozilla0.9.3 stopper, pushing out to mozilla1.0

Comment 18

[Christopher Aillon (sabbatical, not receiving bugmail)]

See bug 102155 for a JS Error that now occurs in this file.

Comment 19

[Paul Chen]

Can't see the entry.postData warning. Marking w4m

Comment 20

[sairuh (rarely reading bugmail)]

mass verification of WorksForMe bugs: to find all bugspam pertaining to this,
set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM".

if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:

a. that it's still a problem with ***recent trunk builds*** on the all
appropriate platform[s]

b. provide clear steps to reproduce (unless a good test case is already in the
bug report), making sure it pertains to the original problem (avoid morphing as
much as possible :)