Context menu slow on certain spellcheck words. (Dutch dictionary)




Spelling checker
7 years ago
3 days ago


(Reporter: Dorus Peelen, Unassigned, NeedInfo)



8 Branch
Windows Vista

Firefox Tracking Flags

(Not tracked)




7 years ago
User Agent: Mozilla/5.0 (Windows NT 6.0; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243

Steps to reproduce:

Using the Dutch dictionary, i typed the following word in a text area: "ageresieve". 

Right clicking to correct this word was slow (0.5-1 second by my stopwatch measurement). I noticed other words are a lot faster, trough there is a variation between words, "ageresieve" sure is a worse case.

The en/us dictionary for example, is fast on "ageresieve", so fast i don't notice a difference between opening the context menu on correct words and on "ageresieve". 

Actual results:

The context menu opened slow.

Expected results:

The context menu should open fast (especially repeated action, catching anyone?)

I tested this on both Firefox 8 and the latest nightly.


7 years ago
Component: General → Spelling checker
Keywords: perf
Product: Firefox → Core
QA Contact: general → spelling-checker

Comment 1

7 years ago
Could be a hunspell bug...

Comment 2

6 years ago
Same problem here, with french dictionary and Firefox 16.0.2

Sometimes you want to access the Context Menu, and doing it on the word
"InvalidOriginalJobOrgCouple" is a very bad idea... takes too long !!!

Could you add something like "If the spellcheck takes more than 2 seconds, skip it" ? And, in this case, in the context menu, add a "Force spellcheck" option so that you can still does long spellchecking ?

Comment 3

2 years ago
Do you still see this problem?
Flags: needinfo?(dricks2222)
Flags: needinfo?(Dpeelen)

Comment 4

2 years ago
Yes, still still happens.
Flags: needinfo?(Dpeelen)

Comment 5

3 days ago
Per policy at If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Last Resolved: 3 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.