ytang,

 

Can you reproduce the problem in the following example?

 

 

Keep me posted

 

 

Thanks for your reply.

 

But the example is not like my application. In my previous post, I indicated it works fine when the editor just posts back to itself with being visible. But if you make the editor invisible (Editor.Visible=false) in a postback, then make it visible (Editor.Visible=true) in the next postback, all script elements will be stripped out.

 

Could you please modify your example to add 2 radio buttons: one called "Show Editor" and one called "Hide Editor". When you click the "Show Editor" to postback, set Editor.Visible=true. When you click "Hide Editor", set Editor.Visible=false.

 

When the editor is visible, you can insert some JS code like "<script>alert();</script>" into the content. Then click the "Hide Editor" to hide it. After you clicked the "Show Editor" to bring the editor back, you can see the JS code has been stripped out.

 

 

ytang,

 

Try this example then:

 

 

 

Thank you for your reply.

 

Your example works fine, because it doesn't postback to server side to set Editor.Visible=false to hide the editor. It just set DIV's style to hide the editor on the client side.

 

But it doesn't solve the problem in my application that has to postback to use Editor.Visible=false to hide the editor. In my application I can't just hide the editor on the client side, because I need to do a lot of code conversion on the server side with postback. If it is a bug for CuteEditor with Visible=false, I have to find a workaround to solve the problem, e.g. save the content to ViewState before set Editor.Visible=false, or wrap the editor with a DIV server control so I can hide the DIV control on the server side instead of hiding the editor itself. I haven't tried the second method yet.