Closed Bug 702115 Opened 13 years ago Closed 3 years ago

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

Categories

(Core :: Spelling checker, defect)

8 Branch
x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Dpeelen, Unassigned)

Details

(Keywords: perf)

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.
Component: General → Spelling checker
Keywords: perf
Product: Firefox → Core
QA Contact: general → spelling-checker
Could be a hunspell bug...
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 ?
Do you still see this problem?
Flags: needinfo?(dricks2222)
Flags: needinfo?(Dpeelen)
Yes, still still happens.
Flags: needinfo?(Dpeelen)

WIm, can you reproduce this?

Flags: needinfo?(dricks2222) → needinfo?(fryskefirefox)

I think we can close this 5-9 year old bug, I can't reproduce.

Flags: needinfo?(fryskefirefox)
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.