trigger spell-check of the current word when the context menu opens

NEW
Unassigned

Status

()

12 years ago
5 years ago

People

(Reporter: marcia, Unassigned)

Tracking

2.0 Branch
PowerPC
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

This appeared on Asa' blog post asking for feedback about the spellcheck.

"The "Add to dictionary" command in the right-click menu is very handy. The problem is that this command seems to appear only if some suggestions for the word are found in the current dictionary. If there are no suggestions, then this command does not appear, which is somewhat absurd."

STR:

1. In a text field, type a word such as CSS or weblog
2. Select the word (it should have no squiqqly line since it is not in the dictionary)
3. Context click and note that no suggestion is available, therefore there is no option to add the word to the dictionary;.
I'm having trouble following the STR: if I type weblog or CSS in this bug's "Additional Comments" textarea, they do get suggestions, and if I type mjkfx so I get the (No spelling suggestions) item, there's an Add to dictionary item below that. The only way I can come close to following the STR is to type in the "Whiteboard" field, where since spellcheck is disabled by default for single-line inputs, I don't get a squiggle, I don't get suggestions, and I don't get an Add to dictionary item, because spellcheck is turned off. Am I missing something, or is this a (why, if you can't tell if it's already there?) enhancement request to add arbitrary words to the dictionary from fields where spellcheck is disabled?
(Reporter)

Comment 2

12 years ago
Phil: Sorry for being unclear. In my STR I forgot to state I was typing *just* CSS and nothing else in the line (I used the "Additional Comments" bugzilla text field as well). If I then combine CSS and weblog I do get the suggestion. But the user who reported the issue did not state which words he was hitting that did not have any suggestions, so that makes it a bit difficult to follow up on his issue. I am not sure if he was adding one liners like I did and that is why he as not getting suggestions. Seems the trigger is hitting return or spacebar, and then I do get the suggestion for those two terms.

(In reply to comment #1)
> I'm having trouble following the STR: if I type weblog or CSS in this bug's
> "Additional Comments" textarea, they do get suggestions, and if I type mjkfx so
> I get the (No spelling suggestions) item, there's an Add to dictionary item
> below that. The only way I can come close to following the STR is to type in
> the "Whiteboard" field, where since spellcheck is disabled by default for
> single-line inputs, I don't get a squiggle, I don't get suggestions, and I
> don't get an Add to dictionary item, because spellcheck is turned off. Am I
> missing something, or is this a (why, if you can't tell if it's already there?)
> enhancement request to add arbitrary words to the dictionary from fields where
> spellcheck is disabled?
> 

Ah, so since we don't want to offer to add words that are in the dictionary but haven't yet been checked because the caret is still in-or-next-to them, this is actually "trigger spell-check of the current word when the context menu opens"?
(Reporter)

Comment 4

12 years ago
Yes, that would be a more accurate summary. I have updated the bug summary, thanks.

(In reply to comment #3)
> Ah, so since we don't want to offer to add words that are in the dictionary but
> haven't yet been checked because the caret is still in-or-next-to them, this is
> actually "trigger spell-check of the current word when the context menu opens"?
> 

Summary: No dictionary suggestions found->No Add to dictionary command available → trigger spell-check of the current word when the context menu opens
This bug is part of a query for Firefox bugs that have Status set to NEW, but have version field set to 2.0 or older and have not changed in over 800 days.

http://tiny.cc/forgottennewbugs

If you still see this bug, or if it is still valid with Firefox 3.6.10 or a firefox 4 nightly build, please update the version field and steps to reproduce.
You need to log in before you can comment on or make changes to this bug.