Closed
Bug 278079
Opened 20 years ago
Closed 20 years ago
Spell checker failure
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: bobharvey, Assigned: mscott)
Details
Attachments
(4 files)
Since updating to version 1 a number of things have gone wrong with the spell checker. 1. The bottom left-hand button no longer says 'send' when invoked automatically, just 'close'. This may be deliberate, but I preferred the other method it made more sense. 2. The spell checker does not find mis-spelled workds. See attached screen dump broken_spell1.png 3. Sometimes it pops up when sending with empty boxes, claiming a miss-spelling but with no word displayed at all. I will post a screen dump as soon as I remember to grab one from a message I don't mind publishng.
| Reporter | ||
Comment 1•20 years ago
|
||
| Reporter | ||
Comment 2•20 years ago
|
||
I tried pressing 'ignore' a few hundred times, but the spell checker never moved on from it's null display. I had to close and send without checking.
| Reporter | ||
Comment 3•20 years ago
|
||
This only started happening when I upgraded to version 1.0 It doesn't just happen with usenet postings, it happens with mail as well. It's starting to become a nuiscance, happening nearly every time I send now. I shall be forced to turn off checking soon. The only extension I have is mnenhy, plus some out of date ones that I can't delete because they don't appear in the extension manager despite a periodic window asking if I want to check for updates...
| Reporter | ||
Comment 4•20 years ago
|
||
I just added the GB .xpi file and found that it still can't detect misspelled words.
| Reporter | ||
Comment 5•20 years ago
|
||
Well, since no-one else seemed to be having this trouble I have downloaded a fresh copy of the GB spelling dictionary and installed that. Both problems seem to have vanished, so I'll call it mended. Unless anyone else knows differently.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•