If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

12/17 nightly clean install chokes on wizardHandlerSet.js

VERIFIED WORKSFORME

Status

SeaMonkey
UI Design
P3
normal
VERIFIED WORKSFORME
18 years ago
13 years ago

People

(Reporter: John Morrison, Assigned: Ben Goodger (use ben at mozilla dot org for email))

Tracking

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
I decided to do a 'clean' install of Mozilla with today's builds (Dec 17).

1) Delete the directory where you installed Seamonkey
2) Delete c:\windows\mozregistry.dat
3) Delete the user profile directory, \users50

With either the

   mozilla-win32.zip from 1999-12-17-10-M13/   or
   mozilla-win32-installer.exe from 1999-12-17-08-M13/

when I start mozilla, the profile dialog comes up (as it should) but I
get the following errors (see notes at end for [n]).

      *** Deferring registration of sample JS components
      *** Registering sidebar JS components
      *** Registering sample JS components
      nNCL: registering deferred (0)
      nNCL: registering deferred (0)
      WEBSHELL+ = 1
      WEBSHELL+ = 2
      calling loadpage...
      startPage:: newProfile1_1
[1]   got a request
      JavaScript Error: ReferenceError: arguments is not defined
      URL: chrome://global/content/wizardHandlerSet.js
      LineNo: 105

[2]   got a request
      JavaScript Error: ReferenceError: arguments is not defined
      URL: chrome://global/content/wizardHandlerSet.js
      LineNo: 105

[3]   got a request
      Error: Can't load: resource:///chrome/profile/content/default/null.
      xul (80004005)

[4]   JavaScript Error: uncaught exception: [Exception... "Illegal value"
      code: "-2147024809" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"
      location: "chrome://global/content/widgetStateManager.js Line: 95"]
[5]
      WEBSHELL- = 1
      WEBSHELL- = 0

      C:\JohnStuff\mozbin\moz\bin>

[1] on startup
[2] click first next (from welcome screen)
[3] click second next (set profile name)
[4] click second next again (after first failed to proceed)
[5] click cancel (I'm dead)

I realize that nightly builds are at your own risk, and I don't expect
them to run. But I imagine you might like to know about this. [I also
believe this is Ben_Goodger's bailiwick (wizardHandlerSet.js)]

Comment 1

18 years ago
cc:ing ben
(Reporter)

Comment 2

18 years ago
See also bug #22098, where rginda has "Problem: core JavaScript arguments
object is not defined for js functions embedded in XUL."

Updated

18 years ago
Assignee: don → rgoodger

Comment 3

18 years ago
dup

Updated

18 years ago
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME

Comment 4

18 years ago
Don't see this now ...

Comment 5

18 years ago
Sorry for the spam. changing qa contact.
QA Contact: paulmac → sairuh

Comment 6

18 years ago
verifying on former self (3jrgm)
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.