Closed
Bug 535098
Opened 16 years ago
Closed 16 years ago
shift-F10 context menu content is different from right-click context menu
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 346930
People
(Reporter: rabarberski, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
When composing a message, and with the spell checker set to English-US, when typing shift-F10 (opens context menu on Windows) on a misspelled (i.e. red underlined) word no spelling suggestions appear in the context menu. When doing a mouse right-click on the same word, suggestions do appear on the context menu.
Obviously, this reduces keyboard-only accessibility of Thunderbird.
Reproducible: Always
Steps to Reproduce:
1. create a new message (ctrl-n)
2. In the compose window, make sure that your spell-check is set to english-us (Options > Check spelling > Language > 'English/United Stated' > Recheck Page)
3. Type some words, with a specific word intentionally misspelled. Right-click the misspelled word. Spelling suggestions should appear.
4. Position the cursor in the middle of the word and press shift-F10.
Actual Results:
No spelling suggestions in context menu
Expected Results:
Spelling suggestions in context menu (in bold)
Strange enough, when I use the Dutch spell-checker the context menu is consistent in both cases (mouse right-click and shift-F10)
| Reporter | ||
Updated•16 years ago
|
Summary: shift-F10 context menu content is different from right-click content menu → shift-F10 context menu content is different from right-click context menu
Version: unspecified → 3.0
Updated•16 years ago
|
Whiteboard: dupeme
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Whiteboard: dupeme
| Reporter | ||
Comment 2•16 years ago
|
||
I read about bug 371777 before submitting this one. And I don't see how it is considered a duplicate.
In bug 371777 the context menu does not always appear/hide when it should.
In my bug, the actual *content* of the context menu is sometimes wrong.
If you agree, please unmark as duplicate (I am new to bugzilla and its policies)
Comment 3•16 years ago
|
||
(In reply to comment #2)
> I read about bug 371777 before submitting this one. And I don't see how it is
> considered a duplicate.
> In bug 371777 the context menu does not always appear/hide when it should.
> In my bug, the actual *content* of the context menu is sometimes wrong.
>
> If you agree, please unmark as duplicate (I am new to bugzilla and its
> policies)
Right the cureent duplicate is 346930 - do you agree with that ?
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
| Reporter | ||
Comment 4•16 years ago
|
||
Yes, definitely.
Had missed that one in my search. Sorry for the duplicate.
I'll post my 'language dependent" observation to that bug 346930 .
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → DUPLICATE
Updated•16 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•