Adam,
Sometimes using your sample - since it starts off in basic HTML mode - cannot reproduce the issue. It is obvious from the above videos - that it is occurring in the scenario I present. If you were to make the editor start off like in the above examples - you would see the issue.
I am not doing any thing special - except for setting the following settings - the editor is doing the rest. - as the videos show. I can give you access to server to do the same experiment OR use the following settings:
sEditor.AutoConfigure = CuteEditor.AutoConfigure.Compact
sEditor.ThemeType = CuteEditor.ThemeType.Custom
sEditor.ShowHtmlMode = False
sEditor.FullPage = True
sEditor.ShowPreviewMode = False
sEditor.ShowBottomBar = False
sEditor.EditCompleteDocument = True
sEditor.AllowEditServerSideCode = True
sEditor.TextAreaStyle.CssClass = "EditText"
sEditor.ShowCodeViewToolBar = True
sEditor.EditorWysiwygModeCss = CSSFile
sEditor.EditorBodyStyle = "EditText"
sEditor.EnableStripScriptTags = False
sEditor.ActiveTab = CuteEditor.TabType.Code
sEditor.ShowEditMode = True
sEditor.EnableStripIframeTags = False
sEditor.EnableStripLinkTagsCodeInjection = False
sEditor.EnableStripStyleTagsCodeInjection = False
I do not take pleasure in pointing out issues... and believe it or not - push back just as hard with my clients - BUT all I am doing is setting values with your control.
regards,
Dave