Alright, as a start, open up editor.js (from the "common" template set) and look for a line:
It should be on line 51. Change that 100 to something high - 5000. Then try loading the advanced editor. You're going to see nothing - just a blue screen - for a few seconds, but it should appear eventually (the number is milliseconds - so it should be around 5 seconds).
However, seeing a blank screen for 5 seconds is obviously not an option. The point of that change is just to see that it does actually make a difference.
If it does, I think we can fix the problem by making a couple changes further down: Look for:
it should be just above:
Add another variable named 'twice' on to the end, so that it looks like:
Now, below "function toolbarInit() {" you should see this:
return;
else
clearInterval(tbInterval);
Change that like so (changes in red):
return;
else
clearInterval(tbInterval);
What that will do is make it go through an extra interval loop, thus taking another .1 seconds to allow IE to load properly. My best guess on this is that IE is running the code halfway through loading - so the DIV's (there are 3 - each one contains toolbar buttons) have loaded, but not everything in them (the buttons themselves) have loaded.
Something else you could do is change this:
to 150 or 200 instead of 100. That will slow the toolbar initialization timings down a little and hopefully the extra .15 or .2 seconds will be enough for IE to get its act together. You don't want to make these number too high, however, as that leads to a noticeable delay loading the advanced editor.
Let me know if these changes help - I admit they are a bit of a shot in the dark, but from our previous experience with this problem I think it will help.
Jason Rhinelander
Gossamer Threads
jason@gossamer-threads.com
Code:
innerInterval = setInterval("initInnerIFrame()", 100);It should be on line 51. Change that 100 to something high - 5000. Then try loading the advanced editor. You're going to see nothing - just a blue screen - for a few seconds, but it should appear eventually (the number is milliseconds - so it should be around 5 seconds).
However, seeing a blank screen for 5 seconds is obviously not an option. The point of that change is just to see that it does actually make a difference.
If it does, I think we can fix the problem by making a couple changes further down: Look for:
Code:
var initInterval, toolbars, tb;it should be just above:
Code:
function toolbarInit () {Add another variable named 'twice' on to the end, so that it looks like:
Code:
var initInterval, toolbars, tb, twice;Now, below "function toolbarInit() {" you should see this:
Code:
if (tbs.length < 3) return;
else
clearInterval(tbInterval);
Change that like so (changes in red):
Code:
if (tbs.length < 3 || twice++ < 1) return;
else
clearInterval(tbInterval);
What that will do is make it go through an extra interval loop, thus taking another .1 seconds to allow IE to load properly. My best guess on this is that IE is running the code halfway through loading - so the DIV's (there are 3 - each one contains toolbar buttons) have loaded, but not everything in them (the buttons themselves) have loaded.
Something else you could do is change this:
Code:
tbInterval = setInterval("toolbarInit()", 100);to 150 or 200 instead of 100. That will slow the toolbar initialization timings down a little and hopefully the extra .15 or .2 seconds will be enough for IE to get its act together. You don't want to make these number too high, however, as that leads to a noticeable delay loading the advanced editor.
Let me know if these changes help - I admit they are a bit of a shot in the dark, but from our previous experience with this problem I think it will help.
Jason Rhinelander
Gossamer Threads
jason@gossamer-threads.com
