Setting the Style > BackgroundImage property of the Linear Gauge > Indicator throws the following error:

This doesn't let me customize the Indicator of the Gauge.

When rendering a report to PDF with the accessibility feature enabled - PDF Device Information Settings at a glance - Telerik Reporting, if there is a table/list/crosstab item that contains an item with a Navigate To Bookmark action pointing to the same BookmarkId, the document won't be rendered because of the following error:

System.ArgumentException: An item with the same key has already been added. Key: (table1) Table X=3810 Y=762 Width=2990 Height=1830
   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
   at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
   at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.Visit(Table table)
   at Telerik.Reporting.Processing.Table.Accept(ProcessingElementVisitor visitor)
   at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
   at Telerik.Reporting.Writing.AccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
   at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
   at Telerik.Reporting.Writing.VisualElementWriter`1.StartWriteAccessibilityItem(ReportItemBase item, ElementPageInfo pageInfo, DocumentWriter writer)
   at Telerik.Reporting.Writing.VisualElementWriter`1.WriteClientFocusableItems(T element, ElementPageInfo pageInfo, DocumentWriter writer)
   at Telerik.Reporting.Writing.VisualElementWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
   at Telerik.Reporting.Writing.ReportItemBaseWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
   at Telerik.Reporting.Writing.ElementWriter`1.Telerik.Reporting.Writing.IElementWriter.StartWrite(LayoutElement element, ElementPageInfo pageInfo, DocumentWriter writer)
   at Telerik.Reporting.Writing.WriteStartOperationsDispatcher.Write(IElementWriter writer, LayoutElement element, ElementPageInfo pageInfo, DocumentWriter documentWriter)
   at Telerik.Reporting.Writing.WriteOperationsDispatcher.Write(IElementWriter writer, LayoutElement element)
   at Telerik.Reporting.Writing.WriteOperationsDispatcher.Visit(Table table)
   at Telerik.Reporting.Processing.Table.Accept(ProcessingElementVisitor visitor)
   at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
   at Telerik.Reporting.Writing.WriteOperationsDispatcher.DispatchWriteOperation(LayoutElement element, ElementPageInfo pageInfo)
   at Telerik.Reporting.Writing.DocumentWriter.Telerik.Reporting.BaseRendering.IWriter.WriteStartElement(LayoutElement element, ElementPageInfo pageInfo)
   at Telerik.Reporting.BaseRendering.PageHandler.Telerik.Reporting.Paging.IPageHandler.StartElement(LayoutElement element, ElementPageInfo info)
   at Telerik.Reporting.Paging.PageStartElement.OutputToPage(IPageHandler handler)
   at Telerik.Reporting.Paging.PageElementsLayer.OutputToPage(IPageHandler handler)
   at Telerik.Reporting.Paging.PageContent.Output(IPageHandler handler)
   at Telerik.Reporting.Paging.PageCompositionBase.OutputPageContent(Stopwatch stopwatchOutputContent, PageContent pageContent)
   at Telerik.Reporting.Paging.PageCompositionBase.<>c__DisplayClass124_0.<CreatePageContentOutputTask>b__0()

When the reporting service fails to generate a report document, the Get Document Info request returns a 500 response with the error message thrown from within the reporting engine. However, instead of displaying the error message in the viewport, the Native Blazor Report Viewer displays a message falsely suggesting that the report is still being rendered when the rendering has, in fact, failed.

In the Standalone Report Designer, collection editors, such as the ReportParameter Collection Editor, do not show the context menu when a property is right-clicked, and resetting property values through such windows is not possible.

The Properties window of the designer illustrates the expected behavior.

The Editor-Control for the HTMLTextBox does not use the localized values from the WebReportDesignerStrings.xx.js.

When the Blazor Web Report Designer is closed and then reopened, some of its resources are not loaded the second time around, causing the resize handles to break.

Making sure the following resources are always loaded on the web designer page, resolves the issue.

• <script src="/api/reportdesigner/designerresources/ext_js/jquery.ui-1.12.1.min.js/"></script>
• <link type="text/css" rel="stylesheet" href="/api/reportdesigner/designerresources/ext_styles/jquery.ui-1.12.1.min.css/">

When the latest Kendo UI version is used, the ellipsis in the Web Report Designer's Report Explorer tree are invisible, and the context menus of some report items cannot be opened.

For example, adding shared data sources to a report is not possible because this functionality is accessible through the context menu of the [Shared Data Sources] collection in the explorer tree.

Expected behavior:

Actual behavior:

To work around the issue, use the 2022.3.913 Kendo UI version on the Web Report Designer page.

When I enable accessibility in the Angular Report Viewer, based on the HTML5 Report Viewer, I get the following console error:

Uncaught TypeError: Cannot read properties of undefined (reading '_controller')
at telerikReportViewer:1:15863
at Ce. (telerikReportViewer:1:16167)
at Ce.n (telerikReportViewer:1:26372)
at Ce.trigger (telerikReportViewer:1:26686)
at ce (telerikReportViewer:1:32782)
at Object.updateUI (telerikReportViewer:1:43789)
at telerikReportViewer:1:93236

The report viewer continues being functional despite the error but accessibility text is missing for page number, export, and buttons(incl. parameters area).

In the latest Reporting version, the interface of the report viewer allows users to set the value of a multiselect report parameter to an empty collection but not make it null.

In some scenarios, reports rely on parameters being null to filter their data and this makes them unusable in the latest version.

According to the HTML5 Report Viewer documentation, the persistSession property of the viewer should be set to false by default.

This is not the case for the HTML5 WebForms Report Viewer, the value of its PersistSession property is true by default.

Since the HTML5 WebForms Report Viewer is a wrapper of the HTML5 Report Viewer, it should have the same default values.

The RTF rendering automatically switches to the Tables rendering mode whenever a Crosstab/Table/List is detected in a report. This rendering mode throws an exception whenever the report contains PictureBox with one of the following sizing options.

• Center
• Normal
• Stretch
• ScaleProportional

The RTF export should work with all PictureBox sizing options regardless of the rendering mode.

To work around the issue currently, one can either force the rendering engine to use the Frames rendering mode using the RenderingMode device information property or set the Sizing property of all picture boxes in the report to AutoSize.

Telerik.Reporting.nupkg has a dependency on ResXResourceReader.NetStandard.

Our 3rd party security audit has found the missing Digital Signature of this DLL. A digital signature would aid in verifying its authenticity and integrity.

The labels of the Send Mail form in the HTML5 Report Viewer and its wrappers do not conform to accessibility standards. They refer to form fields using the field's name attribute instead of the id attribute.

The getReportParameters method of the HTML5 Report Viewer omits parameters with unset values that have their AllowNull property set to False.

The reportSource method of the HTML5 Report Viewer can be used as an alternative.

When a report contains multiple DateTime parameters, the viewer assigns the first value to all of them regardless of their default values or the values passed in the viewer's report source.

Additionally, if one clicks the preview button quickly after changing the value of a DateTime parameter, the old value is passed to the service even though the parameter editor is updated. To avoid this, the user needs to wait a second before previewing.

Text boxes formatted with the 'en-US' culture and '{0:C}' format do not use the correct currency negative pattern in .NET Core.

For example, a field with a value of -2.55 should be formatted to '($2.55)' but instead it is shown as ' -$2.55'

When rendering a report that displays an image through the PictureBox item with binary data in multiple threads within a Docker container, the following error is thrown:

Message=Concurrent operations from multiple threads on this type are not supported.
  Source=DockerBlazorApp
  StackTrace:
   at Test.Reporting.Services.ReportService.<>c.<RenderReport>b__4_0(Object innerSender, ErrorEventArgs eventArgs) in C:\Users\dnikolov\Downloads\dockerblazortestappfortelerik\DockerBlazorTestAppForTelerik\DockerBlazorApp\Services\ReportService.cs:line 49
   at Telerik.Reporting.Report.OnError(Object sender, ErrorEventArgs e)
   at Telerik.Reporting.Report.RaiseError(Object sender, ErrorEventArgs e)
   at Telerik.Reporting.Processing.Report.RaiseReportError(ProcessingElement sender, ErrorEventArgs args)
   at Telerik.Reporting.Processing.Report.RaiseError(ProcessingElement sender, Exception exception)
   at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)
   at Telerik.Reporting.Processing.ReportSectionBase.ProcessItem()
   at Telerik.Reporting.Processing.DetailSection.ProcessItem()
   at Telerik.Reporting.Processing.ReportItemBase.ProcessElement()
   at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)