I use the exportBegin event to prevent the default export logic. However, when I do that, the default viewer notification remains, and I have to hide it manually:

                    exportBegin: function (e, args) {
                        args.handled = true; // Set to true to cancel the default export behavior.
                        //...
                        $(".trv-notification").addClass("k-hidden");
                    },

Double-click selection in the expression editor isn't context-aware. In almost every other application, double-clicking selects a token based on its surrounding context — a single field/identifier when clicking on a field, or the word boundary within a string literal when clicking inside quotes. The expression editor doesn't respect these boundaries, so its double-click behaviour is inconsistent with the standard expression-editor behaviour users expect.

Expected: Double-click selects the relevant token based on context (e.g. an individual field reference, or a word within a string literal).

Actual: Double-click selection ignores context and does not match the token/word-boundary behaviour found in virtually all other expression editors and text inputs.

I have graphs in my report. I render them with Skia on Linux. The issue reproduces with Skia on Windows as well.

The legend labels are not aligned well with the color icon, and data labels on a horizontal bar chart (with OutsideEnd) are misaligned as well:

If I open the expression dialog in the Web Report Designer and select one of the available functions, I will see a sample snippet in the third column below the expression area.

This column is not selectable, so I cannot copy the example and test it out. This example should be copyable, so that each function can be easily tested in the report designer.

I am trying to use the following HTML content for the HtmlTextBox item:

<span style="font-weight:bold">Label&nbsp;1:</span>&nbsp;<span>Data&nbsp;1</span> <span style="font-weight:bold">Label&nbsp;2:</span>&nbsp;<span>Data&nbsp;2</span>

However, the non-breaking space between the spans (label 1/data 1 and label 2/data 2) is not preserved.

I have a custom assembly with default 'version', 'culture', and 'publicKeyToken'.

When I reference the assembly in the 'assemblyReferences' element only with its 'name', the Reporting Engine recognizes it.

If I reference it with the full version, '1.0.0.0', it also works.

However, when I set the 'version' to '1.0.0', the Reporting Engine throws, stating that the assembly is not trusted and must be referenced in the 'assemblyReferences' element.

greetings

Summary

When the Web Report Designer is initialized with non-English string resources (via window.telerikWebDesignerResources), the authentication type selector in the Web Service Data Source wizard behaves incorrectly. Even though "Sin autenticación" (the translated value of WebServiceDataSourceNoAuthentication) is visually selected in the dropdown, the wizard behaves as if a different authentication type is selected — displaying additional required credential fields and blocking progression.

The issue does not occur when using English string resources (WebServiceDataSourceNoAuthentication = "No authentication").

---
Steps to Reproduce

1. Configure a Blazor Web Report Designer with Spanish (es-CO) custom string resources using window.telerikWebDesignerResources:

// WebReportDesignerStrings.es-CO.js
export class WebReportDesignerStringsBase {
    constructor() {
        // ...
        this.WebServiceDataSourceNoAuthentication = "Sin autenticación";
        // ...
    }
}

// Load resources before designer renders
window.telerikWebDesignerResources = new WebReportDesignerStringsBase();

2. Open the Web Report Designer in the browser with the Spanish resources active.
3. Add a new Web Service Data Source.
4. In the wizard URL step, observe the authentication selector — it shows "Sin autenticación" as the selected option.
5. Attempt to proceed through the wizard.

---
Expected Behavior

With "Sin autenticación" selected (equivalent to "No authentication"), the wizard should:
- Require only the Service URL field
- Not display credential input panels
- Allow proceeding to the next step without authentication configuration

---
Actual Behavior

Despite "Sin autenticación" being visually selected, the wizard behaves as if a different authentication type (Basic or 2-step) is selected:
- Additional authentication configuration panels appear or are required
- The wizard blocks progression expecting credential inputs
- The behavior is identical to what occurs when "Basic" or "2-step" is selected

---
Root Cause Analysis

The designer's compiled JavaScript (webReportDesigner) appears to compare the selected authentication type against the English string "No authentication" internally, rather than against a stable enum or index value. When the display text is "Sin autenticación", this comparison fails and the wizard falls through to a non-"no auth" code path.

Evidence: applying the temporary workaround of keeping WebServiceDataSourceNoAuthentication = "No authentication" (English text) in the es-CO resources file resolves the issue completely — the wizard functions correctly while all other strings remain in Spanish.

---
Workaround

In the non-English string resources file, keep WebServiceDataSourceNoAuthentication in English:

// workaround: keep English value until Telerik fixes internal comparison
this.WebServiceDataSourceNoAuthentication = "No authentication";

---
Minimal Reproduction

@* ReportEditor.razor *@
@page "/reportEditor"
@using Telerik.WebReportDesigner.Blazor

<WebReportDesigner DesignerId="wrd1"
                   ServiceUrl="apiReport/reportdesigner" />

// Loaded before designer renders via IJSRuntime.InvokeVoidAsync
window.telerikWebDesignerResources = {
    WebServiceDataSourceNoAuthentication: "Sin autenticación",
    // ... other keys
};


---
Additional Notes

- Both es-CO and en-US string resource files contain 971 keys each — the issue is not caused by missing keys.
- The designer correctly picks up the localized strings for all other UI elements; the bug is isolated to the authentication dropdown value comparison logic.
- Confirmed on version 19.1.25.521; not tested on earlier versions.

thank for your attention.

have a nice day.

When I have multiple reports open in the Standalone Report Designer, I am not able to rearrange/reorder them.

Refer to the tab behavior in Visual Studio, where you can drag one tab and move it to be in front of another tab.

When I display a report in a web report viewer, whose service is running on a server where one or more of the used fonts are not available, the first instance of the item(s) that use those fonts is being substituted with another font. The rest of the items do render with the original font, however.

This creates confusion and inconsistency. We should use the substituted font because it's used for measuring when using Print Preview mode in the web viewers, or when rendering to pdf via print/export.

The rendering extensions are currently loaded by the Telerik.Reporting.Processing.RenderingExtensionManager all at once in the main thread when the report processing starts. This is redundant because one report processing requires one rendering extension to be loaded.

Currently, logarithmic axes do not support the LabelStep and MajorStep properties, which makes it difficult to control label density and avoid visual clutter for larger data ranges.

Adding support for these settings (similar to numerical scales), or providing a way to conditionally hide axis labels, would significantly improve readability and axis customization.