When providing both inline JSON and service Url to WebServiceDataSource, in design time the data is requested from the service instead of being taken from the inline JSON to reduce the network load.

The GetResource() endpoint of the AspNet.Core REST service always adds the "Cache-Control" header to the response's headers collection. This causes an exception when such header already exists.

The PDF export produces an invalid document when the accessibility features are enabled and the engine runs in Docker environment with Linux containers.

Exporting a report with enabled accessibility to PDF or TIFF formats results in ArgumentOutOfRangeException.

The labels of the axes and data points of a Bar chart are not correctly placed in PDF rendering when using .NET Core. The Graph is rendered on multiple pages. The appearance on the first page is correct and deteriorates on the next pages.

In.NET Framework, the same report is rendered as expected.

The label connectors are not displayed when the graph contains a second coordinate system, which is configured for non-pie charts, but is not used by the graph series.

Pie chart coordinate system has Category Scale for its Radial Axis and Numerical Scale for its Angular Axis.

The Context Menu does not pop-up when you right-click on a Report Parameter in the Report Explorer of the designer.

When there are two data items sharing the same CubeDataSource with query with parameters, the first data item is rendered correctly and the second one throws the exception 'An error has occurred while processing Graph 'graph1': Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: index.'

The File cache is not cleaned by the REST Service after stopping it. This can be observed with the default cache settings and a report with a large image, and when the File cache is configured explicitly from the 'cache' element of the Telerik.Reporting configuration section.

The TOC is missing when the report is exported programmatically to Word in .NET Core application

When the culture of the thread is the default one, the private font (e.g. "Shadow Brush") will be replaced with a substitute in the Html5 Viewer (e.g. "Verdana") as the viewer does not respect private fonts. This is normal and expected behavior. When exported to PDF the text is displayed with the correct font ("Shadow Brush") but the embedded font as claimed by the Font properties of the PDF document reader is the substitute font ("Verdana").

When the culture of the thread is changed, the private fonts are not respected and not embedded in PDF rendered document at all. The text does not appear.

If the database that is assigned to the report contains empty records, in Linux and Mac the report is rendered on more pages.

If you add the Telerik.WebReportDesigner.Services package to a working .NET Core 3.1 project using Telerik Reporting, the built fails with System.Reflection.ReflectionTypeLoadException

Currently, there is no WebServiceDataSource property for controlling the Timeout for canceling the task for fetching the data. The default value is 100s, as inherited from the HttpClient. In some cases this is not sufficient, causing the cancelation of the task and failure of the report.

It would be nice, if not required by our client, to have 100% Web-based, Rich, Ad-hoc Reporting Solution.
Something similar to the one in ComponentOne Active Report 

On the Print button click, the viewer opens a File Save dialog instead of invoking the Print dialog. Observed with Edge version 79.0.309.71.

Go to page https://demos.telerik.com/reporting/product-catalog?&skinName=default

Open Search dialog.

Type "Accessories" in search field. Wait for results.

Pick last result (Accessories - page 2) from results list. (page 2 will be opened - correct)

Close search dialog and open it again (or just clear search field).

Type "Accessories" in search field again. Wait for results.

Pick last result (Accessories - page 2) from results list again.

Incorrect behavior: page 1 will be opened instead of page 2; and first result item will be highlighted as selected instead of last result item.

Also I met situation when long results list was scrolled up to top but it was unclear how to reproduce it stable.

Please add the the report viewer control to Blazor.

In HTML5 Report Viewer it is possible to intercept a client request (e.g. the request to export a report to a particular export format) and modify it like this:

{"format":"<script>alert(1)</script>","deviceInfo":{"enableAccessibility":false,"enableSearch":true,"BasePath":"/COAT_SIT/api/reports"},"useCache":true,"baseDocumentID":"31d0a1ca0162a3f13e92bf"}

The malicious script will be executed when the error message for a missing export format is displayed in the viewer.

When the user confirms changing the chart type through the "Change Chart Type" dialog window, the graph designer does not get refreshed and still shows the old chart type.

Underneath the graph item is actually changed and if the report is previewed, the new graph layout will be displayed. The current workaround is to refresh the graph designer by changing one of its properties that cause full item refresh - Culture, Graph title, NoDataMessage, etc.