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

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.

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.

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.

I have noticed that the performance of exporting reports has gotten worse in recent releases. After investigating, I found out that this is likely caused by the sheer size of the code in my projects.

To prove this, I created a simple application that renders a report to PDF programmatically. Then, I created 10 000+ dummy classes in the same project, and tried rendering the report again. The performance was noticeably impacted by this change.

If cells grow or shrink, if there are hidden cells, any time a report section grows vertically, the next section/table is not respecting the growing of the previous item and text prints in the wrong spot or the table overlaps the previous table.

A potential workaround is to manually convert the troublesome tables to lists where possible.

I have a solution with two projects: one containing a report, and another for the objects.

The first one has a project reference to the second, and the objects are used within an ObjectDataSource component in the report from the first.

I open the solution, build the project with the objects, but the Data Explorer of the ObjectDataSource component in the first project with the report does not get automatically updated. I have to reconfigure the ObjectDataSource manually for the change to take effect.

I load multiple variants of the Segoe UI font as private fonts in my application:

			<!-- Segoe UI -->
			<add fontFamily="Segoe UI" path="Fonts\SegoeUI\segoeui.ttf" fontStyle="Regular" />
			<add fontFamily="Segoe UI" path="Fonts\SegoeUI\seguisb.ttf" fontStyle="Semibold" />

This leads to issues, as there is no "Semibold" option in the System.Drawing.FontStyle enum.

The workaround that can be used to avoid this problem is to use unique font family names. For example

			<add fontFamily="Segoe UI" path="Fonts\SegoeUI\segoeui.ttf"  />
			<add fontFamily="Segoe UI Semibold" path="Fonts\SegoeUI\seguisb.ttf"  />