Currently, graph axes do not provide a way to render separator lines between category groups. While this is generally not an issue for simple scenarios, it can make charts with nested categories difficult to read.
For example, when a graph displays multiple subcategories under a parent category (such as revenue ranges grouped by quarter), there is no built-in visual indicator showing where one parent category ends and the next begins.
It would be useful to provide support for category separators on graph axes, allowing report authors to visually separate category groups and improve readability when working with hierarchical data.
When using screen reader applications like JAWS or Narrator, those tools read accessible reporting PDFs in an incorrect order. For example, if I have two items in the report, the reader will read the second item first.
Additionally, images whose AccessibleDescription I have set may be read multiple times..
When I display a report in a web report viewer, whose service is running on a server where one or more of the used fonts are not available, the first instance of the item(s) that use those fonts is being substituted with another font. The rest of the items do render with the original font, however.
This creates confusion and inconsistency. We should use the substituted font because it's used for measuring when using Print Preview mode in the web viewers, or when rendering to pdf via print/export.
Hi Team,
Even after giving the date format facing the inconsistency in the date field for some rows in the table when we export it to CSV file
<TextBox Width="1.036in" Height="0.24in" Left="0in" Top="0in" Value="= Fields.StartDate" Format="{0:MM'/'dd'/'yyyy h:mm tt}" Name="Opened Date">. please see the attachment
Consider adding support for the `start` attribute of the `ol` element in HtmlTextBox. This would allow us to change the start counting:
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.
When exporting an SVG image to PDF, polylines with stroke-dasharray are rendered incorrectly — the dash pattern is not applied.
Additionally, polylines with a stroke-width exhibit visual artifacts such as pixelation or inconsistent thickness.
Step by step instructions or code snippets how to reproduce the problem
If there's no black line with no stroke-dasharray - the red line in a bottom looks correct
test_svg_line_stroke.svg
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xml="http://www.w3.org/XML/1998/namespace" width="500" height="400" viewBox="0, 0, 500, 400" preserveAspectRatio="xMinYMin" transform="scale(1)">
<polyline points="100, 100 400, 100" stroke-width="7" stroke-dasharray="40 40" style="fill:none;stroke:#FF0000;" />
<polyline points="100, 200 400, 200" stroke-width="5" style="fill:none;stroke:#000000;" />
<polyline points="100, 300 400, 300" stroke-width="7" stroke-dasharray="40 40" style="fill:none;stroke:#FF0000;" />
</svg>
test_svg_line_stroke.svg - svg source file
test_svg_line_stroke.trdp - report with a picture box with SVG image
test_svg_line_stroke.pdf - generated PDF file
The rendering extensions are currently loaded by the Telerik.Reporting.Processing.RenderingExtensionManager all at once in the main thread when the report processing starts. This is redundant because one report processing requires one rendering extension to be loaded.
It would be really useful if EntityDataSouce was updated to support Entity Framework Core contexts. EF Core depends on Standard 2.0 so can run on .NET Core or the full framework.
In the Standalone Report Designer File menu, please add the shortcuts next to menu items, like Ctrl + S for Save and Ctrl+Shift+S for Save All.
I changed several reports and then wanted to know how to save all reports at once.