The TOC may be rendered with incorrect font size and incomplete LeaderSymbols when rendered with libgdiplus under Docker with Linux. See the linked screenshot.

It would be helpful to enable printing a table header when no data is available and the NoDataMessage is set. We frequently have tables with one or more static headers that may not have any data - depending on the supplied report parameters. We set the NoDataMessage to display an appropriate message, however, we would like to continue displaying the table title and column headers.

We currently accomplish this with a Panel + Table but that is inelegant. It is more designer friendly to design the table once and reposition and resize it as necessary.

Here is an example screenshot of the issue we have now

If you add the following HTML text that contains two identical paragraphs in an HtmlTextBox, the first paragraph will contain the bold/strong text and the second will not. The specified font family doesn't have a font face for the bold text installed:

<p><span style="font-size: 9pt; font-family: arialmt"><strong>BILLING</strong>&nbsp; The total cost of the hearing aid(s), </span></p>
<p><span style="font-size: 9pt; font-family: arialmt"><strong>BILLING</strong>&nbsp; The total cost of the hearing aid(s), </span></p>

If you use two HtmlTextBoxes to display the two paragraphs, the second HtmlTextBox won't contain the bold text.

When you use a font family, which bold font face is installed, the HTML is rendered consistently.

I have a report with a Graph with BarSeries and DateTime X-axis and Numerical Y-axis. The Series has ToolTip that is displayed correctly in the Standalone Report Designer. However, the Html5 Report Viewer does not display the tooltips. The HTML element for the bars does not contain the needed attributes:

data-tooltip-title="Value" data-tooltip-text="10" data-role="tooltip"

and looks like this:

<path d="M588.32 51.51 L589.05 51.51 L589.05 242.89 L588.32 242.89 Z" fill="none" stroke="lime" stroke-width="2" stroke-dasharray="none" stroke-linejoin="bevel" stroke-linecap="butt"></path>

Please see ticket #1553960 for examples and the initial ticket.

Request: Update isValidXhtml to take in an optional argument that controls whether or not the validation ignores unsupported HTML tags. With the understanding that unsupported tag types do not get output in the HtmlTextBox.

Because the function isValidXhtml evaluates to False for unsupported tag types while the HtmlTextBox just ignores unsupported tag types, there is a disconnect between what the HtmlTextBox can display vs what isValidXhtml allows to be displayed.

This change would allow more flexibility when trying to validate HTML and display it in the HtmlTextBox.

Use case: I have been working a lot with emails and trying to display them within a report. When I use isValidXhtml to validate the email before outputting in an HtmlTextBox, most emails evaluate to False and do not get displayed since they contain many unsupported tag types. However when I remove the validation, more emails get displayed because the HtmlTextBox ignores unsupported tag types. This update would allow more HTML to be considered "valid" by the isValidXhtml function, with the understanding that unsupported tag types will not get displayed.

I have a SubReport in my main report detail section. The TextBox above the SubReport has TocText. The subreport also has items with TocText.

In the final TOC of the main report, the subreport items appear before the main report TextBox, although they are rendered after it.

If I move the main report TextBox from the detail section to the Report Header or Report Group Header section, the TOC order is correct.

Currently we implemented the IDefinitionStorage to read and save files from azure storage

It would be nice if we could call the async methods

If you shrink the browser showing the Blazor viewer, initially the menu toolbar doesn't respond and the right-most menu items get cut. When you continue to reduce the browser width, at some point, the menu becomes responsive and the small menu appears.

The above behavior is reproducible with the Blazor demo application for .NET 6. The problem is not related to the pure Html5 Report Viewer.

The Web Report Designer uses a subset of all available Kendo UI widgets. It will be useful to have a documentation article listing all of them, just as it's done for the HTML5 Report Viewer here: Kendo Widget Requirements.

This way the users will have better understanding which Kendo UI classes and components are used by Web Report Designer and will enable them making their own distribution packages when needed.

The response to the Get Page request of the REST Service in .NET Core/5/6 doesn't include page size when the paper kind is Custom. This may be the reason why the printing from the WPF Viewer results in blank pages.

When the service is in .NET Framework, the paper size is in the response, and the document is printed correctly.

The parameters' area splitter's expand icon gets hidden when the area is shrunk.

I have a TextBox that is rotated at 270 degrees. Its width in some cases is not enough to accommodate the incoming value. I expected it to grow vertically (i.e. in width) in this case. However, its width didn't grow. It just cut the content.

I noticed that if I increased the height of the TextBox, the content was wrapped horizontally.

It would be very useful if the report parameters of all the HTML5-based report viewers become accessible from the report viewer widgets.

For example, we are currently working on a report that has a custom button that sends the current parameters to an API and "signs" the current report (e.g. saves a string in the database and displays it afterward in the report).

This is the outcome in the Standalone designer:

This is the outcome in the WPF viewer: