I am using the ObjectDataSource component of the Standalone Report Designer. However, I get errors mentioning that types from `System.Private.CoreLib` cannot be loaded. This used to work in version 19.3.26.121. The workaround in the latest version is to manually register the `System.Private.CoreLib` assembly in the designer through `assemblyReferences` (File -> Options -> Add).

When an HtmlTextBox contains a large HTML ordered list that exceeds a single page height, the generated PDF is cut at the pixel-level page boundary rather than at a text line boundary. This results in a line of text being visually split mid-glyph — part of the line appears at the bottom of one page, and the remainder is orphaned at the top of the next page.

To reproduce, create an HtmlTextBox that contains an <ol> with lots (>40) <li> items, so they span more than one physical page and export to PDF. Observe the page boundary where the list crosses a page — the split occurs mid-line.

Expected behaviour:
The renderer splits the HtmlTextBox content at a complete line boundary, consistent with how a plain TextBox behaves.

Actual behaviour:
The split occurs at the pixel-level page margin, cutting through a rendered text line.

On export to MS Word, a numbered list that spans two pages restarts at (1) on the second page. Instead, the numbered list should continue numbering from the first page. 

For example, if a list has five items and the fourth item starts on a new page, when I export the report to MS Word, the first three items are numbered (1), (2), and (3), and the last two items are numbered (1) and (2) again.  The last two items should be numbered (4) and (5).

In addition, if an item in a numbered list splits between two pages, the item is numbered twice: once at the beginning of the item and again on the first line that appears on the next page. The line at the top of the second page is numbered (1). This second number should not appear.

The attached file shows both these issues.

WPF report viewer crashes when launching it the second time. The issue appears to occur only when having a trial license activated.

System.Windows.Data Error: 23 : Cannot convert '<null>' from type '<null>' to type 'System.Uri' for 'en-US' culture with default conversions; consider using Converter property of Binding. NotSupportedException:'System.NotSupportedException: UriTypeConverter cannot convert from (null).
   at System.ComponentModel.TypeConverter.GetConvertFromException(Object value)
   at System.ComponentModel.TypeConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
   at System.UriTypeConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
   at MS.Internal.Data.DefaultValueConverter.ConvertHelper(Object o, Type destinationType, DependencyObject targetElement, CultureInfo culture, Boolean isForward)'
Exception thrown: 'System.NullReferenceException' in Telerik.ReportViewer.Wpf.dll
Object reference not set to an instance of an object.

I want to set the Table ColumnWidth to a particular value in the Properties of the Web Report Designer. There is no property ColumnWidth as in the Desktop designers, and I tried to set the Size.Width, which is available.

When I increased the Width from the Properties, in design time, there is no change in the column width, only dashed borders indicating the new size when selecting the corresponding TextBoxes. In runtime, though, the new size is respected.

The inconsistency repeats even when I open the saved report in another browser or through another application, hence this is not a caching issue.

I'm using VS 2022, the demo reporting (Telerik_Reporting_2026_Q1_20_0_26_211). When using the "Telerik Report 2026 Q1 Wizard", I select the following

• "Table Wizard"
• Current Data Sources
• Add New Data Sources
• Select "Object Data Sources
• I select my Assembly and data object.
• I select the Data source Member

See attach file when I finish the wizard.

After updating to the Q1 2026 release of Reporting, I get the following error when passing the value of a DateTime parameter from the main report to a DateTime parameter of a report that I open via the Navigate To Report action:

CSharp.Net10.ReportingRestServiceCorsDemo Error: 0 : Parameter /Date(1771253073461)/ does not match Epoch regex format!
CSharp.Net10.ReportingRestServiceCorsDemo Error: 0 : Parameter /Date(1771253073461)/ does not match Epoch regex format!

The issue seems to occur only when directly passing the value of the DateTime report parameter, so as a workaround, I decided to create a new date using the Date() function. For example:

When using a report parameter of type string whose value resembles a date format (e.g., "3036-01"), the System.Text.Json serialization logic used by Telerik Reporting incorrectly treats the value as a date instead of a plain string. As a result, the parameter is serialized and displayed as a parsed DateTime value rather than the original text, leading to unexpected outputs such as "3036-01-01T00:00:00.0000000":

I have an image set to the checkbox through the CheckedImage property. When I export the report to Excel using the Skia graphics engine, the image is not present at all, or cut off.

The same issue is not present in the GDI engine or with the PictureBox item.

I have created an ellipse shape item and have set its Stretch property to True. Then, I have set the width of the item to be 1.5in, while the height is 1in, which results in a horizontally stretched ellipse on design-time:

However, when I render the report on Linux where the Skia graphics engine is used, the shape is not rendered properly:

The HTML5 Report Viewer uses inline templates which may require enabling the unsafe-eval CSP policy.

The viewer should migrate to using CSP templates as shown in Getting Started with Content Security Policy (CSP) Templates - Kendo UI Templates - Kendo UI for jQuery.

We are using "@progress/telerik-angular-native-report-viewer": "29.26.211"

Seems options Fit to page/Fit to width are mixed

Fit to page does what Fit to width should be doing and vice versa

When using A4 paper or narrow-edge leading media the Web Viewer prints everything perfectly.

When using a 60mm x 30mm label, therefore "wide-edge" leading media, the web viewer prints the label in landscape, even though the print is in portrait!

Just because the media is "landscape" surely it is the print on the media that determines the orientation?

When using the Windows System Print Dialogue this does not occur, on the using the print from the Web Viewer. This is because the Web Viewer converts it to PDF first to print (I believe). Surely, in the code you can state NOT to rotate, OR rotate it back to the correct orientation for wide edge leading media.

The label design is portrait so all the "print / pdf" code needs to do is to query this and not assume that wide edge leading media automatically prints in landscape.

Currently, the desktop viewers don't allow adding custom headers to their requests to the service.
In HTML5-based web viewers, this is possible through the AjaxPrefilter event.

Using the text-indent CSS setting results in part of the text on the first line being cut off:

I use the kendovalidator before rendering the report to check the correct parameter of initial and final date.

However, the validation fails because additional inputs (for the "Send Email" functionality) are included in the HTML output of the viewer even though I have disabled it.

I believe that if the "Send Email" option is disabled the mail data panel should not be created.

I cannot localize the messages of the Angular and React report viewers using the suggested approaches:

• Angular Report Viewer Localization - Telerik Reporting
• Localizing the React Report Viewer - Telerik Reporting

The only alternative is to use the approach from the Localization of the HTML5 ReportViewer Explained - Telerik Reporting article, which I can do only by loading the string resources script in index.html of the SPA.