Completed
Last Updated: 31 Aug 2026 07:22 by ADMIN
Release 2026 Q3 SP1
Sitecore IT
Created on: 29 Aug 2026 13:42
Category: UI for ASP.NET AJAX
Type: Bug Report
0
RadEditor get_html() modifies unfiltered HTML mode content since 2025.4.1111

Regression introduced in: 2025.4.1111

When RadEditor is in HTML mode, calling get_html() without parameters modifies self-closing tags in the returned content.

According to the documented API behavior, the RadEditor client filters should modify the returned content only when the isFiltered argument is set to true. However, the content is currently passed through browser DOM serialization even when filtering is not requested. This normalizes HTML void elements and removes the XHTML self-closing slash.

Steps to reproduce

  1. Add a RadEditor to a page.
  2. Switch the editor to HTML mode.
  3. Enter the following content:
<img alt="" src="image.png" />
  1. Call editor.get_html() or editor.get_html(false).

Actual result

The returned markup is modified and the self-closing slash is removed:

<img alt="" src="image.png">

Expected result

When filtering is not requested, the content entered in HTML mode should be returned without filter-related DOM serialization:

<img alt="" src="image.png" />

Calling editor.get_html(true) may modify the returned content according to the enabled RadEditor client filters.

Impact

Applications that store, compare, validate, or further process XHTML-compatible markup may receive content different from the source entered by the user. This can affect integrations that rely on self-closing tag syntax.

1 comment
ADMIN
Rumen
Posted on: 31 Aug 2026 07:22

Hi,

Thank you for reporting this regression.

The issue has been fixed internally. With the fix, calling get_html() or get_html(false) in HTML mode will preserve the XHTML self-closing tags. Calling get_html(true) will continue to apply the enabled RadEditor client filters as documented.

The fix is scheduled for inclusion in Telerik UI for ASP.NET AJAX 2026 Q3 SP1, planned for release in September 2026.

 

Regards,
Rumen
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources