Foswiki on GitHub is open for business! Next release meeting: Monday September 15, 1300Z

Item9263: TinyMCE autosave breaks on IECollections' IE6

Priority: CurrentState: AppliesTo: Component: WaitingFor:
Urgent Closed Extension TinyMCEPlugin Main.PaulHarvey, Main.KennethLavrsen
Suspect the new code I wrote to use TMCE's built-in formatter engine to set the button states. Ouch. IE6's error dialogues are about as useful as gold on mars

-- PaulHarvey - 06 Jul 2010

The problem is the autosave plugin, but debugging it is proving difficult. I'd like to file a bug to moxiecode but I am doubting my IEcollections copy of MSIE6.

Sorry to do this to you Kenneth, but I set this WaitingFor you because you are the only one I know who has access to a "native" IE6 browser that is not via the IEcollections suite of MSIE browsers

Could you please report the exact IE6 version and whether or not you get a JS error accessing the standard Moxiecode TinyMCE demo: http://tinymce.moxiecode.com/examples/full.php

It might take a minute or two to load the page

Also please report of the wysiwyg editor on trunk.foswiki.org/Sandbox is too slow in your IE6. I have changed our Foswiki integration to use the nice new API provided by TinyMCE, but it is trying to do a lot more work and seems a bit sluggish.

I might change it so that the button state is only updated max. once per second, instead of on every single cursor movement

Thanks

-- PaulHarvey - 07 Jul 2010

It seems WYSIWYG is only broken on IEcollections IE6, I assume.

Given that 90+% of our foswiki developers who do any testing at all with IE at all (let alone IE6), are doing so with IEcollections, I will try to disable the autosave plugin when userData features are not available.

Otherwise there will only be 1 or 2 of us developers ever testing WYSIWYG with IE6.

-- PaulHarvey - 09 Jul 2010

Ping

Paul what should I be looking for in IE6 and Wysiwyg?

I will gladly try. I have a small Asus Eee with an almost virgin XP where IE is still at 6, plus my work computer is still at IE 6. So I can try things.

But I need to know what to look for.

-- KennethLavrsen - 28 Jul 2010

I need to know if there are any JS errors. You should see an alert icon in the lower-left corner of the IE6 browser window, IIRC - "there were script errors on this page", or some such.

If you're not noticing any weirdness, then it's probably okay.

-- PaulHarvey - 29 Jul 2010

I finally got around to doing this. autosave is disabled for IE browsers that don't expose the userData methods via the JS DOM.

Expected behaviour:
  • IE6 with IECollections - no autosave button, disabled
  • IE6 native - autosave should work Kenneth please test
  • IE7 - autosave should work
  • IE8 - autosave should work

Kenneth, we can close this once you have tested with a real native IE6 browser

Let me know if there are any JS errors

-- PaulHarvey - 29 Jul 2010

I did some basic testing today. And I did not see any javascript errors.

I was not aware we had an autosave feature now. So I did not test that.

I did however find a few new bugs that I also see in FF. Will open bug reports for these.

I will try the autosave tomorrow. How does that work?

-- KennethLavrsen - 29 Jul 2010

Create a new blank topic, then save. Start to type some content, do not save. Leave sit for three minutes, the autosave icon should light up.

Now close your browser and open it up again. Edit the topic. Pressing the autosave icon should bring up a dialogue asking if you want to restore saved content; it should do so.

Every three minutes it is saving a draft of your topic to your local browser storage.

-- PaulHarvey - 29 Jul 2010

I have been testing. I have not seen anything genericly broken in IE6.

-- KennethLavrsen - 01 Aug 2010

I tried with a plain text document with around 250000 bytes. Then I can see slow cursor movement on my Asus Eee 900 MHz Atom machine in IE6.

The slowdown in cursor movement at 250000 bytes can be seen and felt. And it is much slower than it is in 1.0.9. But it is not at a level where you cannot use it at all.

What may be more interesting is that I tried the same on my 1.6 MHz Asus Eeebox and it shows the same in IE8. And again only in trunk version, not in foswiki10. So the slow cursor movement thing is an IE thing. Not only IE6

-- KennethLavrsen - 01 Aug 2010

Ok. I will attempt some optimisation. Need to add this to TMCE release notes

-- PaulHarvey - 02 Aug 2010
 
Topic revision: r17 - 04 Oct 2010, KennethLavrsen
 
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. see CopyrightStatement. Creative Commons License