Please disregard my last post - the dropdowns are being rendered correctly now.  I had a build issue that was preventing the latest version of my custom control assembly from being properly referenced. Thanks for your time & assistance-John 

The issue still exists.  The only difference I saw between your editor config and mine is the setting of the EditCompleteDocument property.  I tried setting mine to True but it had no effect. I didn't see a programmatic setting for RenderItemBorder in your sample, so I'm left to assume it's in your config file? Here is the ...

This worked for the dropdowns that are defined in the config file, but not for the other dropdowns that I am creating programmatically.   I have tried setting the RenderItemBorder property on the RichDropDownList object to true but it had no effect - the item highlighting remained the same (dark blue block).  

The problem is that the dropdowns are inconsistently rendered within the same theme.  I have my editor instance set up to use the Office2007 theme, and while the CssClass and Paragraph dropdowns render correctly, the Font and Size dropdowns do not (neither does a custom dropdown that I've added programmatically).

How can these properties be set programmatically?

When I click on the Css Class or Paragraph dropdowns and mouseover the list items, they are each highlighted by a border.  But when I use the Font or Size dropdowns, the highlighting is a dark blue, solid block that makes the black text inside it very hard to read.  At first I thought this caused by something I had misconfigured in my ...

I am trying to integrate CuteEditor 6.6 into an existing page where it will be replacing another rich text editor control.  The page dynamically creates 6 instances of the editor and places each one in a tab within another vendor's tabbed interface control.  Each tab renders its contents within a single-cell table that is hidden/unhidden ...

Thanks for the timely responses.  Unfortunately I cannot strip all <p> tags from the html as others may be legitimately entered by our end users.  I will have to pursue other options.

Thanks Eric.  I've already tried the BreakElement property but that hasn't helped.  If I understand the documentation, that property is used to determine which tags to insert when Enter is pressed.  In my case, I haven't pressed Enter yet, I'm just typing text.   On your example page, I selected ''Br'' mode and typed the word ...

When I use CuteEditor 6.6 in IE8, it wraps the text I enter with paragraph tags.  I've searched the forums here and apparently this is a known issue, but is there a workaround I can use to prevent the tags from being inserted?  Thanks!