HotKey to FreeSpell only causes Mozills to beep




15 years ago
13 years ago


(Reporter: KairiTech, Assigned: aaronlev)


Windows 2000

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030815
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030815

Highlighting text and using the HotKey to access the FreeSpell utility ( ) causes Mozilla to only beep. If immediately
after the beep the highlighted text is copied using the Edit > Copy from the
Mozilla menu bar FreeSpell displays the error "A sharing violation occurred
while accessing "c:\freeSpellTextFile.tmp." After clicking the OK button the
FreeSpell window opens and operates as expected, substituting corrections in its
own window and when exited updating the highlighted text in Mozilla as expected.

Reproducible: Always

Steps to Reproduce:
1. Highlight text in Mozilla
2. Use the HotKey combination to call up FreeSpell
3. After Mozilla beeps click Edit > Copy on the Mozilla menu bar
4. Click OK in the FreeSpell error window
5. Make necessary changes in the FreeSpell window and exit 
Actual Results:  
I was returned to Mozilla with the selected text corrected as expected.

Expected Results:  
Call up the FreeSpell edit window instead of beeping and forcing you to have to
resort to the Edit > Copy method.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.