I've got to crash but if the problem persists let me know and I'll dig further later and see if I can reproduce it.

Cheers,

Joe

Hi Scott,

I've tried on yet another machine here and still unable to replicate the problem.

By any chance  are you using a proxy server for your internet connection? If so do you have it set to bypass the proxy for localhost in the Firefox connection settings?

Joe

I almost can't believe it but I was able to reproduce this problem tonight, not in branches/2.1 but in trunk.
I went to change the textarea in the Contact Form to use the FCKeditor because I had forgot to do this in trunk when I made this change in 2.1 quite a while back.
I opened the page first  then coded it up to use the editor and it doesn't render the toolbar. I stepped through the code and it is rendering the iframe but the toolbar won't display for some reason. It works fine in IE and the editor also works in the forums and other modules. But on the page where I opened it first as a text area then changed it to the editor its like its cached something that is blocking the toolbar. I've tried clearing the cache and all the private data but it just seems stuck.

I step through the fckeditor server side code and it does exactly what it should as far as I can tell.

I'm hacking around with it now trying to see if anything I do resolves it.

Totally weird but I think it is the same problem and may be a firefox bug of some kind from the latest update.

Hey Dean,

Yes the javascript console is showing a whole bunch of errors as shown below. Whats even weirder is it works in the other modules, I'm just getting the behaviour in the contact form. The javascript console shows the same errors on the pages where the editor is working.