Using an Editor demo available from the demos, switch to HTML view and paste the following HTML into it:

<div class="row g-3">
<div class="col-6">
<h4>Left column...</h4>
<br />
This selector will match any element that has a class attribute starting with "col-". For example, it will match elements with classes like "col-1", "col-2", "col-header", etc.<br />
<br />
</div>
<div class="col-6"><span>Right column...</span></div>
</div>

Now, switch again to the Design mode.

Try to add some text after the "Right column..." text by placing the cursor in the end of the text, pressing enter and writing something, or just try to change that text format into an H4.

Editor will insert a new paragraph with the col-6 class and outside that DIV!

Here's the result:

<div class="row g-3">
<div class="col-6">
<h4>Left column...</h4>
<br />
This selector will match any element that has a class attribute starting with "col-". For example, it will match elements with classes like "col-1", "col-2", "col-header", etc.<br />
<br />
</div>
<div class="col-6"><span>Right column...</span></div>
<p class="col-6"><span>Just want to add more text...</span></p> --> this should not be here!
</div>

How can this be fixed? Need to provide some snippets but they are unusable this way.

Thank you

Rad Editor is stuck in time. Today's web content is structured using DIVs, leaving tables for presenting data.

Examples like Telerik Web UI Editor Editable DIV Content Area Demo | Telerik UI for ASP.NET AJAX are so obsolete and shows that this control has been left behind. 

Will you ever support creating contents using DIV elements with a dialog box that allows to add CSS classes or define style settings?

Trythis in a dos box

regsvr32 softpub.dll
regsvr32 wintrust.dll
regsvr32 initpki.dll
regsvr32 dssenh.dll
regsvr32 rsaenh.dll
regsvr32 gpkcsp.dll
regsvr32 sccbase.dll
regsvr32 slbcsp.dll
regsvr32 cryptdlg.dll

It fixed all problems!

2025 Q4 Release strips inline base64 encoded image source by default. 

With the introduction of the new StripJavaScriptUris content filter that is enabled by default as part of the DefaultFilters,  we are seeing inline base64 encoded image source data completely erased. 

For example an image that looks like this:

<img src="data:image/jpeg;base64,/9j/4AAQSkZJRgABAAEAYABgAAD//gAfTEVBRCBUZWNobm9sb2dpZXMgSW5jLiBWMS4wMQD/...." />

becomes

<img src="" />

Is this the intended behavior for this content filter?   

I was able to correct this by adding the following attribute to my <telerik:RadEditor> tag:

ContentFilters="RemoveScripts,StripDomEventAttributes,EncodeScripts,StripCssExpressions,FixUlBoldItalic,IECleanAnchors,MozEmStrong,ConvertTags,ConvertFontToSpan,OptimizeSpans,ConvertToXhtml,IndentHTMLContent,ConvertCharactersToEntities,RemoveExtraBreaks"

Essentially its the same as DefaultFilters, minus the new StripJavaScriptUris.

Please advise...

-Mark

If the user selects the highlighted text individually (by double clicking their mouse and highlighting the words) and paste it into an Editor, all is good.

However, if the user triple clicks to highlight the entire sentence and then paste that into an Editor, this is what shows up in the HTML view:

<div>
<div id="ctl00_Main_Content_ctl00_Main_Content_RadMultiPagePanel">
<div id="ctl00_Main_Content_RadMultiPage">
<div id="Main_Content_SummaryPage">
<div>
<div>Please load claims from QNXT Production 09/12/2025 into Test Reports.</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div id="ctl00_Main_Content_ctl00_Main_Content_ddlQuickLinksPanel">
<div id="ctl00_Main_Content_ddlQuickLinks" tabindex="0">&nbsp;</div>
</div>
</div>
</div>
</div>

Hello Telerik Team,

Our customers identified a few accessibility concerns related to the RadEditor Image Manager and Document Manager popup windows:

1. Keyboard Focus on Popup Activation
   When a user tabs to the Image Manager plugin and presses Enter, the popup window opens. However, keyboard focus does not automatically move into the popup. Instead, the user must press the Tab key again to shift focus manually.
   ➤ To meet accessibility standards, focus should move directly into the modal or popup when it appears. This ensures that keyboard and screen reader users can interact with the dialog immediately without navigating through background content.
2. Missing Dialog Roles and Labels
   The dialog containers ( see below ) currently lack appropriate accessibility roles.
   ➤ Each dialog container should include role="dialog".
   ➤ If the dialog has a visible title, it should also include aria-labelledby referencing the ID of that title element. This allows assistive technologies to announce the dialog context clearly.

Is there any way to fix these two issues?

Thanks,

Lan

Hello Telerik team,

Our customer reported that the Telerik RadEditor table plugin is not accessible using the keyboard. I tested it on the RadEditor demo page and confirmed the same issue. Is there any solution for this?

Thanks in advance,

Lan

The tab toolbar items (Bold (B), italic (I), underlined (U), etc.) act like a Tab list (one can be selected), but when we navigate on it, the screen reader announces the role as a link, which is confusing.

Also, with the role link, the user is not getting enough information about which one is currently selected (visually with colour indication). The screen reader announces as 'Bold, link'.

The recording is attached in the zip file.

Hi Team,

We are using the Telerik RadScheduler control in our ASP.NET Web Application, configured with a Timeline view and vertical resource grouping. Appointments are displayed in the content pane, similar to the example provided in the following link, with the key difference being that resource grouping is set to vertical:

We are encountering a UI issue when a user drags an appointment to the first hour in the timeline view. If the appointment is moved slightly beyond the start of the timeline (into the previous period), it visually shrinks in width. Upon triggering the confirmation dialog and selecting "No", the appointment correctly returns to its original position, but its visual width remains reduced. This is corrected only upon a manual page refresh. Images shown below for reference.