I use the exportBegin event to prevent the default export logic. However, when I do that, the default viewer notification remains, and I have to hide it manually:

                    exportBegin: function (e, args) {
                        args.handled = true; // Set to true to cancel the default export behavior.
                        //...
                        $(".trv-notification").addClass("k-hidden");
                    },

When a report is saved in the Web Report Designer, a popup appears confirming that the report was successfully saved. However, it is visible for far too long and blocks users during this time.

This feature request is to add an 'ok', 'hide' or 'close' button to these types of popups so the user can dismiss it.

Thank you,

Shannon

Hi there,

Adding an external style sheet to a report in a report-book triggers an error when previewing the report book, "Object reference not set to an instance of an object" 

I've attached the bare minimum project to reproduce the error.

I've also tried upgrading to R3 2020

Cheers

In my Graph, I have set the AccessibleRole and AccessibleDescription. The alternative text is read correctly by the Acrobat Reader's 'Read out Loud' functionality.

The problem is that it keeps reading it multiple times.

The HTML5-based report viewers send 404 request to `/sass/fonts/kendo-font-icons.ttf` when font icons are being used:

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.

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

1. Save svg content (see below) as a file c:\test_svg_line_stroke.svg
2. Create an empty report
3. Add a picture box
4. Select a value for the picture box - use file c:\test_svg_line_stroke.svg
5. Go to preview - SVG is correct
6. Click Export->Acrobat (PDF) file and export a PDF file
7. Open PDF file to verify that the red line in a bottob does not have stroke-dasharray applied

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.