357467 - Spelling suggestions don't activate when anchor is at the beginning of a misspelled word

Status: RESOLVED INVALID

(Core :: Spelling checker, defect)

Description

[Stuart Morgan]

If the offset passed in to GetMispelledWord is for the position just before a misspelled word, spelling suggestions don't activate.  This is noticeable in Firefox if you click on the first half of the first letter of a misspelled word--unless the previous word is also misspelled, it which case it works--and is even more noticeable in Camino where it currently uses the actual caret position.  In the future Camino will likely pre-select the word, as is normal for OS X, meaning the anchor will always be at the beginning of the word.

Considering a position at the beginning of a range to be inside it for spellchecking seems like it would give a more consistent experience.

Comment 1

[Wayne Mery (:wsmwk)]

Stuart do you see this in v2?

Comment 2

[Stuart Morgan]

I don't know what you mean by "v2", but the latest Minefield exhibits the same symptoms (I'd have to make a custom build of Camino to check Camino, as we've long since hacked around it). Is there some reason to believe this would have been fixed?

Comment 4

[Matt Caywood]

Still a bug. 

Testcase from Bug 385690: 

1. insert the phrase "ctrl-left + ctrl-right" (including quotes) into a text area. 
2. Right-click on the left and right 'c's. 
3. The region that brings up the suggestion dialog is different for each.

Comment 5

[Jens Stutte [:jstutte]]

I cannot reproduce this on current Firefox or Thunderbird.