I have a page with CuteEditor control.  All ie and gecko browsers save fine on both Mac and Windows.

 

On another page,  I have CuteEditor inserted into a user control,  which is included into the parent page using the <% Register ... directive.  This page has problems saving on Mozilla, Netscape, and Firefox on both Windows and Mac.  On Windows IE,  everything works great with this child control. 

The problem maybe lies somewhere within the child control on gecko browsers, because ASP.NET renders the IDs of child controls with the control name's prefix,  it possibly messes something up with the a reference within the CuteEditor template code.  And maybe because of this,  the new text isn't posted back to the page.  Upon postback of this page, the text on the server side is the previous state's text,  resulting in no change reflected.

 

On a side note,  the GetDocument() javascript doesn't work on any Gecko based browser, on both Windows and Mac.

 

I can send you a login/pw to see for yourself.  Just give me an email to send to...

 

 

Thanks.

 

 

binh,

 

>>I can send you a login/pw to see for yourself.  Just give me an email to send to...

 

Please email to Support@cutesoft.net

 

 

GetDocument() javascript is for IE only. We will post the javascript solution for Gecko based browser soon.

 

It has been 3 weeks since I posted this editor in a user control for firefox bug.  What is the status of this issue?

binh,

 

This is an old post.

 

I believe this issue has been resolved in the current version.

 

Which version of CuteEditor are you using?

 

 

 

 

 

 

 

5.2.0.0, build date 2/23/06

 

Can you create a simple aspx page which can demonstrate the problem and send it to me?

 

 

I have sent you an email containing a test account to use on our server.  Mind you that v4.X worked fine with the same code under Firefox and Netscape.  This version breaks Netscape AND Firefox, but works in IE.

 

The strange thing is that doing an alert(editor.GetHTML()); on button click before postback reveals the content is correct.  Putting a break on Page_Load shows that the content reverted back to the previous state.