Using build 20020408 on winxp and linux if the user has installed a spellchecker it they try to open a 2nd incident of the spellchecker they don't get a warning that it's already in use. 1. Launch mail and open 2 compose windows, type in some incorrectly spelled text 2. Launch the spellchecker on one of the compose windows 3. Switch to the other compose window and click spellcheck Result: nothing happens, all toolbar buttons are not working, user can't even Send the message that isn't using spellchecker Expected: A warning message that the spellchecker is being used (this is what 4.7 does). This will at least let the user know why the buttons aren't working

--> over to cmanske

Is this a regression or is this new functionality we need to add? How critical is this problem? (This bug is not nominated for nsbeta1, should it be?)

This isn't a limitation of the dialog, it's the spell check engine. Once one instance is initialized, I see " Exception error: InitSpellChecker" when trying to start 2nd instance.

Adding a warning would be easy. Nominating for nsbeta1.

This WFM with mozdev spellchecker (BuildID 2002112018 trunk). Is this a Netscape-only bug or was this fixed?

Composer triage team: nsbeta1-

This works fine in current builds. Two instances of the spellchecker can be invoked and function properly.