Closed
Bug 136995
Opened 22 years ago
Closed 21 years ago
with spellchecker installed, user won't get warning when trying to open a 2nd incident of the checker
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
mozilla1.2beta
People
(Reporter: esther, Assigned: cmanske)
References
Details
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
Comment 2•22 years ago
|
||
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?)
Assignee | ||
Comment 3•22 years ago
|
||
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.
Assignee | ||
Comment 4•22 years ago
|
||
Adding a warning would be easy. Nominating for nsbeta1.
Updated•22 years ago
|
Comment 5•22 years ago
|
||
This WFM with mozdev spellchecker (BuildID 2002112018 trunk). Is this a Netscape-only bug or was this fixed?
Comment 7•21 years ago
|
||
This works fine in current builds. Two instances of the spellchecker can be invoked and function properly.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•