TinyMCE: Spellchecker plugin freezes IE6

What do you mean with "crashes"? Could you please ensure that this bug also happens after (temporarily) disabling other contrib modules?

Without further information I'm forced to mark this issue won't fix.

I can confirm that IE6 was locking up hard (needing a force quit) trying to process a tinymce text field. Problem *not* with wysiwyg api, but rather related to tinymce spellchecker plugin. The hard freeze in (IE 6 only) was dependent on the spellchecker plugin being enabled. Will investigate upstream.

Re-opening this issue for your convenience. If necessary, I'd be happy to remove the spellchecker plugin, since it's only compatible to IE anyway.

However, no one of you mentioned the installed version of TinyMCE yet. Does this also happen with TinyMCE 3.x?

Also, you might want to have a look at TinyMCE's bugtracker at SourceForge for existing/related issues.

My apologies. This is with tinymce 3.x and the 6.x-1.x-dev release of WYSIWYG API (Dec 5 or 6th build). The spellcheck plugin did work fine with firefox and safari, but would leave ie6 hanging. This is without even clicking the button. Just loading the tinymce enabled textarea would bring down ie6. I enabled the spellchecker plugin by adding the following stanza to the tinymce.inc plugins section.

'spellchecker' => array(
'path' => $editor['library path'] .'/plugins/spellchecker',
'buttons' => array('spellchecker' => t('spellchecker')),
'url' => 'http://wiki.moxiecode.com/index.php/TinyMCE:Plugins/spellchecker',
'internal' => TRUE,
'load' => TRUE,
),

Any updates? Did you open or find a corresponding issue in TinyMCE's bugtracker? This issue certainly won't fix here, so all I'm waiting for is a link to an existing issue (probably on SourceForge).

Without further information I'm forced to mark this issue won't fix. Feel free to re-open this issue.

Hey guys,

I am using the latest TinyMCE 3.2.1.1 and I believe the Spellchecker doesn't work even though the button shows up assuming you followed #5's comments. TO get it working try this version of spellchecker. Replace the existing spellchecker plugin in the TinyMCE plugin folder with this and it should now work like a charm.

Denis

Check out this thread http://drupal.org/node/350480#comment-1177259 for info on getting Drupalbreak to work as well.

I can verify that the problem does exist with drupal 6, and latest version of TinyMCE. It started with a lot of users complaining their computer freezes when trying to post. I use Firefox so never noticed it. When I tried IE6, the moment you try to post something the whole computer freezes. The only way to get out of it is hard shut down, or CTRL+ALT+DEL and closing iexplore process.

You can stop it from happening if you unched all plug-ins and buttons, but that defeats the purpose. Looking for an alternative, which really sucks. The best one I found so far is Nicedit, (works on both IE and Firefox), but has issues when it comes to editing.

FWIW, I'm pointing to #352938: TinyMCE 3: IE6: Memory leak with Forecolor button - however, that issue is not tied to any spellchecker. IE6 is completely screwed up with TinyMCE 3 currently.

Fournd an alternative to TinyMCE that works both for Firefox and IE, and has just as sleek GUI, and features. It's called FCKEditor.

If you go into settings for the editor admin/settings/wysiwyg/ and then uncheck "enable by default" will this stop the IE from freezing, or does the editor still load (just waiting for someone to click "enable rich-text")? I'm looking for a solution for myself on this.

I can confirm that enabling spellchecker causes IE6 to completely lock up forcing a hard escape or restart.

My system:

Drupal 5.x
Wysiwyg 5.x-1.x-dev (2/1/09)
TinyMCE 3
Latest spell checker from Moxiecode
Patches from #10 and this thread http://drupal.org/node/352938 applied.

Run the setup without spellchecker and the editor loads nicely (including img_assist).
Enable spell checker as described in #5 and enable spellchecker button and system locks.

Sun, do you need any more information to re-open the issue? Let me know how I can help even though I have no clue how to debug something like this in IE...

------

On a related note, it's interesting built-in-to-the-browser textarea spell checking (you know, the little red underscrores that automatically show up when you mistype) works in the TinyMCE editor on Safari and not Firefox. I wonder if that can ever come back...

A little more detail on this (5.14 Tiny MCE 3.2.1.1) is that IE uses a boatload of ram and just keeps sucking it up until it starts paging.

Just to let people know - I've created Wysiwyg SpellCheck module that enables TinyMCE spellchecker plugin. It may be just what you need, until there is a better approach to Wysiwyg plugins.

Can anyone confirm if it also crashes or freezes IE6? If yes - please file a bug to the project.

I can also confirm that this problem exists. I even set up a test site with nothing but Drupal 6.10 and an empty database, WYSIWYG 1.6, tinymce 3.2.1.1, imce_wysiwyg v 1.1 and IMCE 1.11.2.6 in an attempt to track down the problem.

If any of Spellchecker, Forecolor or Backcolor are checked, IE6 will freeze, consuming between 40% and 90% of the processor time.

This happens when tinymce is selected as the editor for either filtered HTML or full HTML. If the default is set to disable RTE then the page will load, but will freeze when the RTE is enabled from the page. Similarly, if tinymce is only enabled for full HTML and the page default is filtered, the page will load fine but freeze when full HTML is subsequently selected.

Another, possibly related, issue concerns the IMCE button. If that is selected, the editor buttons will not appear in IE6. If the disable RTE option is selected, the edit-body area will sprout a resize handle, the option will change to enable, and the IMCE link to Insert Image or Link will appear below. Clicking enable makes the Insert Image link and resize handle vanish, but the editor buttons never reappear. I say this may be related, because the page will load fine even with Spellchecker, Forecolor and Backcolor all selected. (but of course, they can't be used because there's no buttons... )

Everything works just fine in Firefox 3. If only I could get all my users to upgrade from MS!