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

I have projects on .NET Core and I want to use the System.Text.Json serializer that is the new default, but reporting relies on Newtonsoft.Json.

---

ADMIN EDIT

There are two approaches that can be taken right now to solve this:

OPTION 1: define separate endpoints (services, projects) for the different tasks - they can still use the same database layer through a shared project, depending on the architecture you have. This would let you have separated services with the appropriate serializers without custom attributes and code (see below). For example, create a separate project for the reporting REST services.

OPTION 2: add some custom decoration on the endpoints so you can choose which serializer is used on each, you can find some examples here: https://stackoverflow.com/questions/59650907/how-to-configure-two-json-serializers-and-select-the-correct-one-based-on-the-ro - the point being to register a serializer depending on the endpoint based on your own code rather than let the framework put one in for all endpoints.

NOTE: This would be a breaking change.

---

Description
Even though there is no map wizard for the WRD, it is possible to create a map item and try to set it. However, it is not possible to select an ESRI Shapefile for the spatial data or inspect the already existing one in the report:

Steps To Reproduce

1. Use the PopulationDensity report
2. Open the ShapeMapSeries:

4. The Source type can't be configured:

Expected behavior
Even with no map wizard in the WRD, the map item should be created from scratch, and all properties should be editable.

Actual behavior
The Source Type doesn't show any option for selecting shape files.

The attached report generates different PDF documents when rendered by the Standalone Designer and REST Service, both targeting the .NET Framework 4.6.2:

• The PDFs have different sizes
• When using the 'Read out loud' functionality of the Adobe Reader, the items are read in a different order. The order in the PDF generated by the designer is correct, and the one in the service-generated PDF is wrong.

My report has a Text Watermark as part of the PageSettings, and is configured for Accessibility. The report contains a Page Header and Page Footer. In the Page Footer, there are two TextBoxes.

When I generate an accessible PDF with Telerik Reporting and use the Adobe Reader > Read Out Loud functionality, it doesn't read the content of the second TextBox in the Page Footer.

Some of the Web Report Designer pop-up messages are not localizable. For example, the message about trying to access a report that does not exist on the server:

Related to:

https://feedback.telerik.com/reporting/1635210-attempt-by-security-transparent-method-telerik-reporting-openxmlrendering-spreadsheet-workbook-ctor-to-access-security-critical-method

Also affects Telerik.Reporting.Processing and Configuration: Attempt by security transparent method 'Telerik.Reporting.Processing.AssemblyRefManager.LoadAssembliesCore()' to access security critical method 'Telerik.Reporting.Configuration.ReportingConfiguration.get_Current()' failed.

Currently, the GetDesignerResource endpoint of the Web Report Designer service is case-insensitive, which can lead to issues if the URL is made lowercase at some point, such as by a URL rewrite rule, or similar scenarios.

For example, the following reference to the Web Report Designer script will load return the file:

<script src="api/reportdesigner/designerresources/js/webReportDesigner"></script>

But if lowercase is used, for example, like this:

<script src="api/reportdesigner/designerresources/js/webreportdesigner"></script>

The request will return a 404(Not Found) response.

Using Blazor native reporting component.  Our underlying email sending service requires that Subject is not blank, however the UI does not validate the Subject field.

Need to be able to validate that Subject is not blank when user attempts to submit email form.

We are experiencing issues with Telerik Reporting related to RTL text (culture 'ar-JO') rendering, as outlined below:

• Text wrapping is not working correctly within the HTML5 Report Viewer. The text seems to overflow the TextBox.
• When exporting to PDF, the text exceeds its boundaries, does not wrap as expected, and in some cases is cut off.

I'm getting an error in Telerik Report Designer (Data Explorer): "Member x on type String not found"

The version is: 19.3.25.1119

Steps to Reproduce:

• Open SRD.NET.
• Configure the Assembly References through the SRD.NET UI to include a DLL.
• Open an existing report file.
• Observation: The Data Explorer tool window is populated correctly, showing all fields and methods as expected.
• Close Telerik Report Designer.
• Re-open Telerik Report Designer.
• Verify that the Assembly References are still correctly configured (they are).
• Open the same report file.
• The Data Explorer is not populated. Instead, it throws an error:

Please note the spelling error in the k-notificaiton-error class name. Should be k-notification-error:

<div class="trv-parameter-error k-notification k-notificaiton-error" style="">
                <span class="k-notification-status k-icon k-i-x-outline"></span>
                <span class="trv-parameter-error-message k-notification-content">Parameter value cannot be empty.</span>
            </div>

Because of this, error messages are rendered with incorrect color (should be red):

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.

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..

I had an issue with watermarks being present in the generated PDF despite the license validation passing. In the trace log, I was seeing this:

x.x.x.x.exe Information: 0 : *** ReportProcessor.ProcessReport STARTED ***
x.x.x.x.exe Information: 0 : SQLite x64: v3.50.4
x.x.x.x.exe Information: 0 : 
x.x.x.x.exe Information: 0 : *** ProcessReport #0 "Invoice" STARTED ***
x.x.x.x.exe Information: 0 : *** ProcessReport #0 "Invoice" DONE in 00:00:00.6363067 ***
x.x.x.x.exe Information: 0 : 
x.x.x.x.exe Information: 0 : *** ReportProcessor.ProcessReport DONE in 00:00:00.7891276 ***
x.x.x.x.exe Information: 0 : 
x.x.x.x.exe Information: 0 : License check for assembly Telerik.Reporting, Version=19.3.25.1119, Culture=neutral, PublicKeyToken=a9d7983dfcc261be: True
x.x.x.x.exe Information: 0 : 
x.x.x.x.exe Information: 0 : *** Render Report #0 "Invoice" STARTED ***
x.x.x.x.exe Information: 0 : ReportName: Invoice; DocumentName: Invoice; Extension: PDF
x.x.x.x.exe Information: 0 : DeviceInfo Contents
x.x.x.x.exe Information: 0 : ===================
x.x.x.x.exe Information: 0 : ChangingPermissionType: ""
x.x.x.x.exe Information: 0 : ComplianceLevel: "None"
x.x.x.x.exe Information: 0 : CopyingPermissionType: ""
x.x.x.x.exe Information: 0 : DocumentAuthor: ""
x.x.x.x.exe Information: 0 : DocumentCreator: ""
x.x.x.x.exe Information: 0 : DocumentKeywords: ""
x.x.x.x.exe Information: 0 : DocumentNaturalLanguage: ""
x.x.x.x.exe Information: 0 : DocumentProducer: ""
x.x.x.x.exe Information: 0 : DocumentSubject: ""
x.x.x.x.exe Information: 0 : DocumentTitle: ""
x.x.x.x.exe Information: 0 : EnableAccessibility: "False"
x.x.x.x.exe Information: 0 : EndPage: "0"
x.x.x.x.exe Information: 0 : FontEmbedding: "None"
x.x.x.x.exe Information: 0 : ForceLicenseWatermark: "True"

The issue turned out to be due to caching, but the output puzzled me while I was debugging this. Turned out `ForceLicenseWatermark` is always true (the misleading part), but only has an effect when the license validation fails.

After dragging a report viewer control from the Visual Studio toolbox to the surface of a Windows Form, the viewer is added to the component tray but it is not added to the Controls collection of the form. Thus, the viewer is not displayed when running the application.

Also, some properties of the report viewer, such as the ReportSource property, are not serialized properly after being modified through the Visual Studio properties window.

Currently, one can work around these issues by manually editing the InitializeComponent component method of the form's .Designer.cs file.