Spellcheck suggestions not visible in context menu



4 years ago
4 years ago


(Reporter: Instantbot, Unassigned)





4 years ago
*** Original post on bio 689 by deOmega <jahkae AT gmail.com> at 2011-02-09 19:54:00 UTC ***

Right-clicking  on a misspelled word in the text input area of a conversation does not bring up spelling suggestion.

Windows 7
version 0.3a2pre (20110209042124)

(Noticed in previous versions as well)

This is from the error console:

Error: uncaught exception: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIInlineSpellChecker.getMisspelledWord]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: resource://gre/modules/InlineSpellChecker.jsm :: <TOP_LEVEL> :: line 89"  data: no]

Comment 1

4 years ago
*** Original post on bio 689 by deOmega <jahkae AT gmail.com> at 2011-02-09 19:56:51 UTC ***

here is link to an image of the issue:

*** Original post on bio 689 at 2011-02-10 12:09:25 UTC ***

Steps to reproduce:
1. Check that the suggestions work.
2. Paste a huge amount of text in the textbox.
3. Notice that you no longer have suggestions, even after removing the huge text.

When the context menu fails to display suggestions, I see the JS error mentioned in comment 0. On my Mac debug build, just before the JS error I have this in the terminal:
WARNING: NS_ENSURE_TRUE(editor) failed: file /Users/florian/buildhg/hg.instantbird.org/mozilla/extensions/spellcheck/src/mozInlineSpellChecker.cpp, line 1608
WARNING: NS_ENSURE_SUCCESS(res, res) failed with result 0x80004003: file /Users/florian/buildhg/hg.instantbird.org/mozilla/extensions/spellcheck/src/mozInlineSpellChecker.cpp, line 833

And repeated a few times (both before and after the JS error), I see this, which may or may not be related:
WARNING: NS_ENSURE_TRUE(content && range) failed: file /Users/florian/buildhg/hg.instantbird.org/mozilla/editor/txtsvc/src/nsFilteredContentIterator.cpp, line 285
Ever confirmed: true
OS: Windows 7 → All
Hardware: x86 → All
You need to log in before you can comment on or make changes to this bug.