Error in res/profile/navigationFinish.xul

VERIFIED FIXED in M9

Status

defect
P3
normal
VERIFIED FIXED
20 years ago
3 years ago

People

(Reporter: mozillaBugzilla, Assigned: gayatrib)

Tracking

Trunk
x86
Windows 95

Firefox Tracking Flags

(Not tracked)

Details

After I click finish when adding a new profile when M8 starts up, I get the
following message displayed in the console window under Win 95. I don't have any
other machines to test this on.

Inside the Exit Wizard function...
DATA IS: ProfileName=mozProfile%ProfileDir=%
Created nsProfileCore
Entered Create Profile RoutineEntered Start AppRunner Routine
Run AppRunner with profile -> mozProfile <-
Created nsToolkitCore
JavaScript error: parent is not defined
URL:
file:///C|/MARCUS/MOZILLA-WIN32-M8-FULLCIRCLE/X86REL/res/profile/navigationFinis
h.xul LineNo: 48

This only happens when I've deleted mozregistry.dat.
This occurs on NT also.  Apprunner launches on both machines despite error
message.
If you do not delete mozregistry.dat, and create a new profile, the transition
from Profile Manager to apprunner shows no error messages
Assignee: selmer → racham
Target Milestone: M9
Bhuvan, please investigate the deleted mozregistry.dat angle on this bug and
then fix or forward to Gayatri as appropriate.  Thanks, Steve
Assignee: racham → gayatrib
This may be because of the additional toolkitCore's CloseWindow call in the
navigationFinish.xul.
The link with deletion of mozregistry.dat is that CreateProfileWizard comes up
every time mozregistry.dat is deleted and navigationFinish.xul belongs to
CreateProfileWizard.
Reassigning to Gayatri (gayatrib@netscape.com).
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Removed the additional toolkitcore close in navigationFinish.xul
Status: RESOLVED → VERIFIED
verified on Win95, build 1999072808
Component: Profile Manager → Profile Manager BackEnd
Moving all Profile Manager bugs to new Profile Manager Backend component.
Profile Manager component to be deleted.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.