I have the Cute Editor nested in an outer DIV. Upon first page load the Cute Editor functions as normal. When I relocate the outer DIV (and with it the Cute Editor) in DOM via appendChild it breaks. Specifically, I'm appending it to the body and then back again to its original location in the DOM. Interestingly it works perfectly in IE7, but not in: FireFox, Opera, or Chrome.

 

Do I have to do anything special to inform the control to reload itself?

 

When it breaks, Cute Editor will not let me populate it programatically or by typing in a value. It won't even show the cursor.

freedom9ner,

THanks for your attention. I'm not familiar with the property DesignMode, does it belong to CuteEditor?

 

Is it possible to dynamically create and delete CuteEditor object via JavaScript. Or was the intention to use it only in a static state?

>>THanks for your attention. I'm not familiar with the property DesignMode, does it belong to CuteEditor?

 

No, this property belongs to the browser.

 

 

>>Is it possible to dynamically create and delete CuteEditor object via JavaScript.

 

Cute Editor is a not simple JavaScript Editor, every thing can be created from client side.

 

It's a server control. It must be created at the server side.

 

Through DHTML and JavaScript trickery I was able to implement a different round-about solution to avoid appendChild. In the process I noticed Opera does not properly render CuteEditor if it's initial display is set to none. More accuratly, it's containing DIV is set to none (CuteEditor attributes are untouched). Upon setting it's containing DIV to default/block, CuteEditor appears but the editing window is condensed. The toolbar is visible.

 

Can anyone confirm similar problem? Any reason Opera would do this? Luckily I was able to use visibility, but that does not solve my curiosity as to why opera would mangle the editor.