Last Comment Bug 914462 - Spell check doesn’t work when check as typing in Email and news with mail.compose.max_recycled_windows = 0
: Spell check doesn’t work when check as typing in Email and news with
Status: NEW
Product: SeaMonkey
Classification: Client Software
Component: MailNews: Composition (show other bugs)
: SeaMonkey 2.21 Branch
: All All
-- normal with 5 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
Depends on:
  Show dependency treegraph
Reported: 2013-09-09 19:53 PDT by Phillip M. Jones, C.E.T.
Modified: 2014-08-27 07:35 PDT (History)
6 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Phillip M. Jones, C.E.T. 2013-09-09 19:53:29 PDT
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Firefox/24.0 SeaMonkey/2.21 (Beta/Release)
Build ID: 20130819194341

Steps to reproduce:

Spell check is set to check words as Typed supposed to underline word in red the when clicked on a list of suggestions are supposed to show up. 

Actual results:

Not spell checking even though checking is on

Expected results:

if I typed any word incorrectly a red line should immediately show up. And clicking on red line show as list of suggested words. 

NOTE: Check before sending does work (which hasn't in years on Mac version caused crashes) 

And both work on Browser. 

Mac OSX.8.4 SM 2.21a
Comment 1 User image Philip Chee 2013-09-21 11:17:08 PDT
I don't know if this is a Duplicate or not but see:
TB Bug 919184 - Spell as you type option not working/Not checking spelling
TB Bug 917027 - "check spelling as you type" periodically breaks for the duration of the process
TB Bug 910848 - inline spell checking not working
Comment 2 User image Phillip M. Jones, C.E.T. 2013-09-21 21:02:16 PDT
917027 is similar but applies to windows version of Thunderbird. Started in version  above, still applies in in the latest version 25 and is permanent deal. Oh and by the way now using OSX.8.5.

919184 symptom sounds almost the same except for linux and also appears to be for TB.

910848 Symptom again Linux  Thunderbird but symptom similar. I'd say 917027 is the closest.
Comment 3 User image Michael Lueck 2013-09-27 05:09:15 PDT
I can confirm this bug on Linux installed from the official Mozilla build installed via UbuntuZilla.

Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 SeaMonkey/2.21

Most annoying! Please change this to a confirmed cross-platform bug.

For me, sometimes it marks words correctly, other times not. I do not believe I have restarted SM and this morning it is again working as expected.
Comment 4 User image Phillip M. Jones, C.E.T. 2013-09-28 12:48:36 PDT
Still the same: here is current information about the version of SeaMonkey I am using:

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Firefox/24.0 SeaMonkey/2.21
Build identifier: 20130908221205

I have set as advertising at as Firefox

OSX.8.5 Update.
If it appears in other Platforms please change to Multi-platform
Comment 5 User image Jay O'Brien 2013-09-29 17:18:21 PDT
I really need speel chk when tipeing!  Please somebody?  Thanks.
Comment 6 User image Hartmut Figge 2013-09-29 19:38:57 PDT
According tp Phillip setting mail.compose.max_recycled_windows to 0 helps. Same workaround as in
Comment 7 User image Phillip M. Jones, C.E.T. 2013-09-30 10:52:30 PDT
Asked Hartmut to Comment so far it has fixed the issue. Evidently when this problem showed up some how code has changed to set 1 instead of 0

Thank you Hartmut for commenting.
Comment 8 User image gwelsh 2013-09-30 19:03:02 PDT
Interestingly, from  :


---> If set to a number greater than zero, compose windows will be recycled quicker. Defaults to 0. 

So it was supposed to be zero all along.  Anyone know wth "recycled" is?  GW
Comment 9 User image Jay O'Brien 2013-09-30 21:13:20 PDT
I have a computer running XP that is still on SeaMonkey 2.20. mail.compose.max_recycled_windows is set to 1 and spell check when typing works fine. In my opinion 2.21 did not change it to 1, it was there already.
Comment 10 User image gwelsh 2013-09-30 23:26:36 PDT
Then the incorrect setting was apparently not detrimental (not recognized?) until 2.21.  I'm not a developer. I don't even know the use of that setting, only that adjusting it to what it was supposed to be, fixes this new problem. GW
Comment 11 User image Michael Lueck 2013-10-01 04:49:14 PDT
@Jay #9, in fact, 1 is the default value. So setting it to 0 is adjusting it from its default value.

Setting it to 0 myself for the first time now.
Comment 12 User image Phillip M. Jones, C.E.T. 2013-10-01 11:21:56 PDT
I'll make no further comments as Developers or Bug fixers now know what is broken and needs to be fixed. No it the Job of the Bug fixers to fix the issue. Rather than having to use a workaround.

Note You need to log in before you can comment on or make changes to this bug.