John Morrison Reporter
	Description • 22 years ago

This doesn't seem right.

1) Install mozilla 1.2.1

2) Create a new profile, then exit the application

3) Open XUL.mfl in emacs and search for 'classic.jar' and 'modern.jar'.
   The first one matches, the second one doesn't. Ok, that's expected
   behaviour.

4) Start the browser, switch to the modern skin, and then exit the app.

5) Open XUL.mfl in emacs and search for 'classic.jar' and 'modern.jar'.
   First one matches, second doesn't, but that still seems reasonable.

6) Start the browser (you are now using the modern skin), and then exit 
   the app.

7) Open XUL.mfl in emacs and search for 'classic.jar' and 'modern.jar'.
   First one matches, second doesn't. Why isn't modern in the dependency 
   list for XUL.mfl?

8) Start the browser, open Composer (which is a window/dialog that you have 
   not used before), and then exit the app.

9) Open XUL.mfl in emacs and search for 'classic.jar' and 'modern.jar'.
   First one matches, and now the second one does too.


I'm not sure if this leads to any serious problem, but I thought I'd mention
it as a possibility.

	John Morrison Reporter
	Comment 1 • 22 years ago

By the way, I think this may also apply to third party themes (and to classic.jar
in builds where modern.jar is the default). You don't get the skin jar added to 
the dependency list until you use a dialog/window that you haven't used before.
For some 'well worked-in' fastload files, that's potentially never.

	Robert Kaiser
	Comment 2 • 15 years ago

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 3 • 15 years ago

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 4 • 15 years ago

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 5 • 14 years ago

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420