Firefox spell checker not working in contentEditable areas

Description

Trunk.
Use Visual Editor.
Enter bad spelling. I use "This is a hgihd test."
Note that hgihd is not underlined in Firefox 3.0.3.
Right click field, turn off spell checking.
Right click field, turn it on again. Word will become underlined.

This is basically the same problem as #3856. The solution there was to force gecko_spellcheck to true. I checked the code, and that solution is still in there, so somewhere, a change to the TinyMCE code must be disabling this. I notice some code in the TinyMCE advanced theme that has comments along these lines, but I am not familiar enough with TinyMCE to work out what that does.

Why not unify the functionality across browsers, and set Autocheck to off? It always works correctly when you hit the button, and that way, you'd only have to hit it once instead of twice... and it could make it into 2.7. ;-)

Confirming that I get this behavior a lot. Firefox 3.0.x's built in spell check on WordPress 2.7 is intermittent and random. Seems worst when typing new post, but sometimes happens intermittently when revising existing post.

Being bold and bumping to "major" severity because A. I'll bet proper spelling is important to most people and B. Firefox's spell check works in other apps.

After reading this thread I wonder how this is related to Wordpress?
You're talking about Firefox's built in spell checker and TinyMCE. Both of which have nothing to do with Wordpress code. (Granted WP does integrate TinyMCE)

If words underline noting misspellings while using TinyMCE maybe you should contact Firefox or TinyMCE devs, or both.

also, since this isn't my thread.. I would suggest someone change this to a severity of Minor or Trivial.

No, this seems to be Firefox spellchecker/iframe/contentEditable bug that has been around for a long time (since FF 1.5 I think). It's intermittent and hard to build test case for.

Did quite a bit of testing some time ago trying to determine what triggers it but couldn't pinpoint it exactly. Seems to be affected by some specific css and/or js dom manipulations but not consistently. Seen something similar happen in some versions of Thunderbird too although the cause may be unrelated.

The spellchecker in WebKit browsers seems to work properly.

+1 to closing this as invalid. If someone comes up with a workaround I'll be glad to add it but don't think this is WordPress bug.

As I've mentioned multiple times, disabling auto-check fixes the issue, and makes the the behavior consistent on both browsers. In clicking the button or right-click Spell Check on Firefox, it worked perfectly fine every time.

By browser consistency you mean turning off the built-in spellchecker in Firefox, Safari and Chrome because IE doesn't have one? Don't think so.. Everyone expects to have a spellchecker in all textareas except IE users.

Actually, no. It's hit or miss which browsers that it "automatically" starts in. In Firefox, it's broken when it automatically starts, and not working at all. Thus, for "browser consistency," turning off the Auto-Start made complete sense, especially given that the spell check actually WORKS when you hit the button.

I wish some of you had just answered the funtionality question --- "is it supposed to auto-check? Or are you supposed to hit the button?" from five months ago --- instead of being so ridiculously pedantic about it now. Because, well, even still --- it's never been answered, and from a Dev perspective, it's something that needs to be addressed, rather than just voting it off the island.

Basically, this has gone way off topic. Blame whatever ... meanwhile, there's a valid fix there that makes it work on every browser out there. But oh well. *shrug*