We're running into two major issues with Cute Editor 5.2 (and 5.1) within our ASP.NET application.  The first is purely cosmetic.  Any dropdown lists fail to properly position the list of items on the page (see attached figure).

 

The second issue is more serious.  The control does not seem to properly handle formatting requests.  For example, I can select text and apply a font to the text.  If I then try to set the font size, very frequently either the font size will not be applied or the size is applied but the font type is lost.  This makes using the Cute Editor for rich text editing very frustrating for the end-user.

 

Any ideas why we're seeing these kinds of issues?  I can get you access to our web site to look at the problems in the application if that would help.

 

rsholtes,

 

The first issue is a DHTML issue. The javascript in your page has some conflict with CuteEditor client scripts.

 

For the second issue, can you reproduce the problems in the following example?

 

 

Tip:

 

If you have the following HTML code:

 

 

If you select the "World" and "test", then apply a font, you will get the following result:

 

If you select the "World" again, and apply a font size, you will get the following result:

 

You should get the following result:

 

 

Intead of

 

 

This feature is by design.

 

You can turn off this feature off by setting Editor.UseFontTags Property to true.

 

Editor.UseFontTags Property

Font tags are now deprecated, meaning that they aren't used any more and will cause validation errors. Many legacy pages still contain style information in font tags. By default Cute Editor converts font tags to span tags. <font face="times" size="4" color="#ffffff">your text</font> would be replaced with <span style="font-family: times, serif; font-size: 110%; color:#ffffff">your text</span> If you still want to use font tags, you can set this property to true.