Firefox Spell Check unchecked by default in Quick Reply

J_L · 25. Apr 2010, 07:53 AM

It was mostly unnoticeable/forgettable, and I thought it wasn't worth reporting, until now.

Usually, Firefox Spell Check is enabled by default on every text box on the web page. An exception to that is the Quick Reply used here in Gizmo and the Wilders Security Forum (and probably everywhere else that uses this quick reply). In these place it is disabled by default, and I have to right click > Check Spelling to enable it. Other than that, it works just fine.

Is there a solution to this problem?

vasa1 · 25. Apr 2010, 08:01 AM

I have to click "post reply" or "quote". I can't type directly in the quick reply box. It's grayed out.

With either of the two possibilities, spell-check is working by deefault.

It caught "deefault".

vasa1 · 25. Apr 2010, 08:29 AM

Oops! I foind the "quick reply" thingy and spell-check doesn't work for me either (FF3.6.3).

Ritho · 25. Apr 2010, 12:16 PM

So that is why we have some posts with such atrocious spelling. And here I was blaming it on a break down in our education systems.

shruggy63 · 28. Apr 2010, 09:50 AM

Have a look through this. It's under point 10) I think.
http://maketecheasier.com/28-coolest...cks/2008/08/21
It worked for me but I'm not necessarily recommending it :-)

J_L · 28. Apr 2010, 11:41 PM

Quote:

Originally Posted by shruggy63

Have a look through this. It's under point 10) I think.
http://maketecheasier.com/28-coolest...cks/2008/08/21
It worked for me but I'm not necessarily recommending it :-)

I already enabled it. This problem only occurs in quick reply, not normal reply.

vasa1 · 29. Apr 2010, 06:11 PM

Quote:

Originally Posted by Ritho

So that is why we have some posts with such atrocious spelling. And here I was blaming it on a break down in our education systems.

Blame the Tweeting Twits for the cud and the gud and the wud. And of course, b4 Twitter was d gr8 SMS

.

(That's my last post like that. Promise. E. & O.E.)

J_L · 28. Mar 2011, 12:10 AM

Sorry about reviving an old thread, but the issue is fixed by Firefox 4.

25. Apr 2010, 07:53 AM	#1 (permalink)
J_L Co-Author, Best Free Security List Join Date: Dec 2008 Posts: 1,475	Firefox Spell Check unchecked by default in Quick Reply It was mostly unnoticeable/forgettable, and I thought it wasn't worth reporting, until now. Usually, Firefox Spell Check is enabled by default on every text box on the web page. An exception to that is the Quick Reply used here in Gizmo and the Wilders Security Forum (and probably everywhere else that uses this quick reply). In these place it is disabled by default, and I have to right click > Check Spelling to enable it. Other than that, it works just fine. Is there a solution to this problem?

25. Apr 2010, 12:16 PM	#4 (permalink)
Ritho Foundation Editor Join Date: Apr 2008 Location: Planet Earth Posts: 1,391	So that is why we have some posts with such atrocious spelling. And here I was blaming it on a break down in our education systems. __________________ The smallest good deed is better than the greatest intention.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

25. Apr 2010, 08:01 AM	#2 (permalink)
vasa1 Senior Member Join Date: Mar 2010 Posts: 400	I have to click "post reply" or "quote". I can't type directly in the quick reply box. It's grayed out. With either of the two possibilities, spell-check is working by deefault. It caught "deefault".

25. Apr 2010, 08:29 AM	#3 (permalink)
vasa1 Senior Member Join Date: Mar 2010 Posts: 400	Oops! I foind the "quick reply" thingy and spell-check doesn't work for me either (FF3.6.3).

28. Apr 2010, 09:50 AM	#5 (permalink)
shruggy63 Member Join Date: Jan 2009 Posts: 12	Have a look through this. It's under point 10) I think. http://maketecheasier.com/28-coolest...cks/2008/08/21 It worked for me but I'm not necessarily recommending it :-)

28. Mar 2011, 12:10 AM	#8 (permalink)
J_L Co-Author, Best Free Security List Join Date: Dec 2008 Posts: 1,475	Sorry about reviving an old thread, but the issue is fixed by Firefox 4.