Bug report

NORM.S.INV, NORM.INV, and NORM.DIST are officially listed as supported formulas, but they are not functioning properly

Regression bug since 2024.4.1112

Reproduction of the problem

Open the Demos - https://demos.telerik.com/kendo-ui/spreadsheet/index

Paste: =NORM.S.INV(0.908789)

Result must be 1.3333347

Environment
Kendo UI version: 2024.4.1112
Browser: [all ]

Hi!

I am loading Kendo-UI via npm (@progress/kendo.ui:2025.4.1321). The @progress/kendo-ui package internally references @progress/kendo-charts^2.9.0. At the time I installed kendo-ui, the latest available version of @progress/kendo-charts was 2.11.0, which is why npm chose this one.

However, this version leads to a JS error when rendering bar charts similar to this one:

Error: <g> attribute transform: Expected number, "matrix(NaN,NaN,NaN,NaN,…".

This is caused by line 374 in @progress/kendo-charts/dist/es/chart/chart.js (version 2.11.0). It has been added in version 2.10.0. If I am using version 2.9.0 instead (which is also served by the CDN for Kendo-UI 2025.4.1321), everything works fine.

Is there an issue in the supported version ranges of the dependencies of @progress/kendo-ui?
Or does @progress/kendo-charts not follow the rules of semantic versioning?

I would like to avoid pinning the versions of all sub-dependencies of Kendo-UI just to avoid running into such conflicts when running "npm update".

Bug report

If a Popup is open and you click a Menu item, the Menu prevents the Popup from closing automatically.

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/IrEYAqaK/2
2. Click the Open/Close button
3. Hover the Menu item and click the sub-item.

Current behavior

The Menu prevents the Popup from closing

Expected/desired behavior

The Popup should close when the Menu item is clicked.

Environment

• Kendo UI version: 2022.2.621
• Browser: [all]

Hi!

I have noticed the following behavior of the Kendo-UI MultiSelect widget (reproducible in this DOJO):

1. focus the button
2. click on the X button of the selected tag in the MultiSelect to remove it

-> the button is still focused

The user has interacted with the MultiSelect, so it should grab the focus. Since the tag is removed, I would have expected the whole widget to be focused instead. At least this is what happens when clicking the "clear" button.

The Kendo-UI Diagram widget supports moving the whole diagram using the pan() method. However, the given offset does always have to be absolute.

Consider the following example:

The diagram is zoomed in and therefore not fully visible - assume a current offset of (-100, -100). The users should be able to pan using keyboard shortcuts. Whenever pressing one of the arrow keys, the diagram is moved in the corresponding direction by e.g. 50px:

If the user presses [ArrowRight], pan() needs to be called with an offset of (-50, -100).
If the user presses [ArrowUp], pan() needs to be called with an offset of (-100, -150).

However, since I do not know how much the diagram has already been moved, I cannot set the absolute offset required.

I have seen that pan() returns the current offset when being called without arguments, but this is not documented. Is this safe to use for that purpose or is there a better alternative? If yes, the documentation should be updated.

As all grids, the kendo Gantt chart's rows change their color when hovering. However, the background overlaps the border between columns and makes them disappear for the hovered row.

You can reproduce the described behavior by hovering one of the rows in this DOJO.

Bug report

If the ColorPicker tools in the Editor are configured to render a gradient, you cannot type in the HEX/RGB inputs.

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/AWEmUSOS/7
2. Open one of the Color tools.
3. Try to type in the inputs.

Current behavior

The inputs are not selectable and you cannot type in them.

Expected/desired behavior

The inputs should be selectable so that you can type in them.

Environment

• Kendo UI version: 2023.2.829
• Browser: [all]

Bug report

In the Spreadsheet, when users scroll horizontally to columns that are not initially visible, then activate Freeze Panes, the Spreadsheet scrollbar behave incorrectly

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/zYbZtYDR.
2. In the Spreadsheet, scroll horizontally to columns that are not initially visible.
3. Activate Freeze Panes.
4. Attempt to continue horizontal scrolling.

Current behavior

When Freeze Panes is activated after horizontal scrolling:

• The Spreadsheet snaps back to the first (leftmost) column, Column A.
• Horizontal scrolling becomes unusable.
• Users cannot navigate to the right-hand columns until Unfreeze Panes is selected.

Expected/desired behavior

• Activating Freeze Panes should retain the current horizontal scroll position.
• Horizontal navigation should remain fully available across all unfrozen columns.
• Freezing should not disable the internal Spreadsheet scrollbar or shift the viewport.

Environment

• Kendo UI version: 2026.1.212
• Browser: [al]

In the latest version of Kendo UI, various input controls like the NumericTextBox or the ColorPicker now consist of an input field and a button control (used for increasing/decreasing the value or opening the dropdown).

The border-radius for those widgets can be controlled by setting the "rounded" option. At the same time, when using SASS themes, a button's default border-radius might be set using the $kendo-button-border-radius variable. The buttons inside e.g. a NumericTextBox do not override the theme's border-radius which leads to an outcome like this:

Widgets that use Buttons internally (and therefore offer no way of overriding the button's border-radius by setting its "rounded" option manually) should override the default styles.

Unfortunately, I could not reproduce the behavior in a DOJO, because I cannot transpile SASS themes there.

Consider the following scenario: There is a sortable Kendo-UI grid with a corresponding dataSource. Initially, the dataSource contains some items. When updating the dataSource to an empty array, all items disappear from the grid - so far, so good. However, if a column header is clicked afterwards to sort that column, the removed data reappears again.

We created a small "walkthrough" in this DOJO to demonstrate the issue.

FYI: The issue can be avoided by using a custom implementation of dataSource.transport.read which always returns the latest data.

The Typescript definitions for Kendo UI define the kendo.ui.ToolBarOpenEvent as follows:

interface ToolBarEvent {
        sender: ToolBar;
        preventDefault: Function;
        isDefaultPrevented(): boolean;
}

interface ToolBarOpenEvent extends ToolBarEvent {
        SplitButton?: JQuery | undefined;
}

The event is also documented that way in https://docs.telerik.com/kendo-ui/api/javascript/ui/toolbar/events/open. However, the corrersponding method in kendo-toolbar.js:446-453 does the following:

open: function (e) {
    var isDefaultPrevented = that.toolbar.trigger(OPEN, { target: element });
    if (isDefaultPrevented) {
        e.preventDefault();
        return;
    }
    that.adjustPopupWidth(e.sender);
},

Chart Series provide a toggleVisibility() method that allows to hide some data points of the series (or all of them) from the user. However, setting the first series to invisible breaks the chart's keyboard navigation.

This DOJO demonstrates the behavior: For the sake of simplicity, the first of the two series is toggled invisible right after the chart is rendered, but this may happen at any other point in time. Click anywhere in the DOJO's output area. Press TAB to focus the chart. The following error is logged in the browser console:

Uncaught TypeError: Cannot read properties of undefined (reading 'options')
    at init.focusVisual (kendo.all.min.js:9:4230266)
    at init._focusElement (kendo.all.min.js:9:4410242)
    at init._focusFirstPoint (kendo.all.min.js:9:4409100)
    at init._focus (kendo.all.min.js:9:4407358)

Bug report

Pivotgridv2 measure is not slicing the data by the second attribute when expanding


Reproduction of the problem
Open this Dojo example - https://dojo.telerik.com/zmhjamtb

Value sum is correct (sliced) for all rows:

where the second row is expanded and not correctly sliced:

Environment

jQuery: 3.4.1

Kendo UI version: 2025.1.227
Browser: [all]

I have noticed that, after switching themes, the tooltips in our application do no longer work correctly. I was able to reproduce the issue in the following two DOJOs:

• Correct behavior: https://dojo.telerik.com/eFOcahIS (stylesheet https://kendo.cdn.telerik.com/2022.2.510/styles/kendo.default.min.css)
• Invalid behavior: https://dojo.telerik.com/ahOkibow (stylesheet https://kendo.cdn.telerik.com/2022.2.510/styles/kendo.default-ocean-blue.min.css)

The only difference between those two is the stylesheet to be loaded (line 6).

Steps to reproduce:

1. load the DOJO
2. hover over the red dot (notice how the text uses all space available and does not get wrapped unless necessary)
3. hover over the green dot 
4. hover over the red dot again

In step 4, the correct behavior would be displaying the tooltip in the same fashion as in step 2. However, in the faulty DOJO, it can be seen that the tooltip does not expand past the width of the text that is displayed when hovering over the green dot. This means that when displaying long tooltips after short ones, they are always wrapped unnecessarily.

A way to fix this behavior (and what's actually the difference between the two stylesheets) is to set the position on the ".k-animation-container" back to its default value "static". Usually, this value is overridden by the output of the size calculations, but during the calculations this value comes to play.

This third DOJO demonstrates the fix described above.

Please note that when using the default-ocean-blue stylesheet, the positioning of the callout seems to be broken as well.

Bug report

In the Scheduler, if we have a slotTemplate and at the same time views.virtual, the resources().field in the slotTemplate always returns the same value (of the first resource).

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/lJnddiLz

Current behavior

The data-resource='#= resources().user_id #' in the slotTemplate always has the same value.
If the virtual is disabled, the data-resource='#= resources().user_id #' has a value based on the resource.

Expected/desired behavior

The resources should be correctly returned in the slotTemplate even if the virtual option is enabled.

Environment

• Kendo UI version: 2025.3.1002
• Browser: [all ]

If you create a grid with editable set to true, selectable set to one of the multiple options ("multiple, row" or "multiple, cell"), batch set to true and a column with editing disabled (either through the model or through the columns editable property), then when you update an editable cell and click the non-editable cell in the same row the "Save changes" and "Cancel changes" buttons do not appear.

See https://dojo.telerik.com/zAKmmTEU and attached example.html.zip

Notes:

Editable is disabled using a JavaScript function for UnitsInStock

{ field: "UnitsInStock", title: "Units In Stock", width: 120, editable: function() { return false; } },

Editable is set to false in the schema model for Discontinued

Discontinued: { type: "boolean", editable: false },

In this example, if you change the value of a UnitPrice cell and then click one of the non-editable cells (UnitsInStock or Discontinued) in the same row, the UnitPrice cell will be marked as dirty, but the "Save changes" and "Cancel changes" buttons will not appear.

This appears to happen because of the following:

• The focusout event is triggered on the grid.
• The closeCell method is called from the tap event registered on the cell.
• The _destroyEditable method is called within the closeCell method.
• The _editContainer field is set to null in the _destroyEditable method.
• The closeCell method is called again from within the editCell method but returns early because the _editContainer field is null.
• The timeout anonymous method from the focusout event handler is called, but the _toggleToolbarEditingItemsVisibility method is not called because _editContainer is null.

Stack trace:

See attached image.png for an example image.

Bug report

Reproduction of the problem

Dojo: https://dojo.telerik.com/koWkSInz

Expected/desired behavior
The notification should default to options.button, but should use args.closeButton to decide to show the close button in the notification.

Environment
**Kendo UI version: 2025.2.520
**jQuery version: 3.7.1
**Browser: [all]