Gossamer Forum
Home : Products : Gossamer Forum : Discussion :

Advanced editor toolbar corrupt sometimes

Quote Reply
Advanced editor toolbar corrupt sometimes
HI,

I have a user with IE 5.5 that has the advanced editor toolbar display corrupt sometimes. I updated the editor.js file to the version from GForum 1.20 (even though I still have 1.18 because I have so many mods).
editor.js,v 1.9.2.1 2003/04/15

I have not seen this with IE 6.0, Is this a known problem or is his computer the problem?

Here is a screen shot.

Thanks for any help.



----------
Michael J. Challis - CRUZN8R - PT Cruiser Club - http://www.ptcruiserclub.org

http://www.ptcruiserclub.org/forum
Quote Reply
Re: [CRUZN8R] Advanced editor toolbar corrupt sometimes In reply to
Unfortunately, I've seen it on IE 6.0. Reloading the page often helps. Doesn't seem to be any rhyme or reason that I can figure out as to why it happens, except I've only seen it when replying to or editing a message.
Quote Reply
Re: [agaffin] Advanced editor toolbar corrupt sometimes In reply to
He said it happens at work and at home on different computers. One is IE 5.5 and one is IE 6

The Minor Issues list of 1.2.0 states: "A fix for the issue with advanced editor showing up scrambled is present. This fixed is believed to correct all outstanding corruption issues related to the loading of the advanced editor."

Am I the only one reporting this after installing the 1.2.0 editor? Maybe I did not get the latest version or I missed something else in a template or something. I still use 1.1.8 scripts, but I have updated some things in templates to 1.2.0

----------
Michael J. Challis - CRUZN8R - PT Cruiser Club - http://www.ptcruiserclub.org

http://www.ptcruiserclub.org/forum
Quote Reply
Re: [CRUZN8R] Advanced editor toolbar corrupt sometimes In reply to
Unfortunately, the "fix" that I mentioned in the release post had to be removed, as it was causing other serious and consistent problems. There's a post around here somewhere about adjusting the interval timings in editor.js, which unfortunately is currently my best solution.

Jason Rhinelander
Gossamer Threads
jason@gossamer-threads.com