FCKEditor does not work in Mozilla

I think the problem is that your FCKeditor is matching sizes with the textarea, which is display:none, and therefore sized x:0,y:0

A solution would be to start the page with visibility:hidden and display:block on the div, then after FCKeditor has been initialised, change it to visibility:visible and display:none

Kae

I have a similar problem... I create an FCKEditor within a hidden DIV and make the DIV visible when the user clicks a button... in IE7 this works fine but in FF2 the edit area (textarea?) is transparent and I can't edit anything. The border of the editor is visible, as is the toolbar.

If I paste the same code to create the editor elsewhere on my page (i.e. a non-hidden bit) it works fine.

I've tried setting display:block as suggested but it made no difference. My DIV is hidden at page-load time and made 'visible' later- I don't use display:none.

Any advice would be appreciated.

Thanks

ACD

AdamDale3 wrote:I have a similar problem... I create an FCKEditor within a hidden DIV and make the DIV visible when the user clicks a button... in IE7 this works fine but in FF2 the edit area (textarea?) is transparent and I can't edit anything. The border of the editor is visible, as is the toolbar.

I also am having a similar issue in FF. Does your textarea remain empty with each click of your button, or only the first time the button is clicked? See my post to get a better idea of the issue I am referring to:

http://www.fckeditor.net/forums/viewtopic.php?f=6&t=6891#p18364

My problem is solved... unfortunately, and embarrassingly, it was just a typo! I had two quotes on the end of style= statement on a div about 4 miles further up the page which caused the problem... amazingly the 300 lines of code between it and the fckeditor all worked fine and even better, IE managed to handle it and continue working regardless!

ACD

AdamDale3 wrote:My problem is solved... unfortunately, and embarrassingly, it was just a typo! I had two quotes on the end of style= statement on a div about 4 miles further up the page which caused the problem... amazingly the 300 lines of code between it and the fckeditor all worked fine and even better, IE managed to handle it and continue working regardless!

ACD

Those darn quotes. Most of the time when I'm having an issue I take a step back and ask myself what stupid mistake I made. Sometimes it takes a little time to actually figure it out.