We use the KendoUI for jQuery framework in the enterprise SaaS application we create. Giving our clients access to their data and being able to provide a mechanism where a client could build out some of their own functionality on our Saas platform (ie accessing the Data, webservices etc) is highly desirable.
Our front end is based on a MicroUI approach, so if the client can vibecode building a new microUI, the UI experience with the other microUI we provide would be seamless. Examples might be: Create a Scheduler view showing all the European Holidays in 2026, or create a grid view populated with all the customers who have not transacted in 2025 and show their linkedin link/profile.
We can easily wrap any vide coded application into our application now using the microUI approach, but what we dont get is the same look and feel, themes and components being used. It is this we are looking to solve.
I am currently using the ANDI accessibility tool and have encountered an accessibility issue with the tooltip icons across my application.
The tool reports an "Aria-Hidden Alert" stating: "Element is focusable but has or is contained by [aria-hidden = true]." The tool also reports as "Keyboard Access Alerts" which states" "Focusable element is not in keyboard tab order; should it be tabbable"?
The HTML for these elements shows aria-hidden = true and focusable = false. I believe the focusable attribute should be set to true.
I have attempted to resolve this using JavaScript to directly removing aria-hidden = true and changing focusable to true. However, there is no built-in configuration in Kendo UI for ASP.NET MVC to customize these accessibility attributes for tooltip icons therefore it didn't work.
Can you make the icons customizable?
I am including a screenshot of the code.
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)
Environment
Kendo UI version: 2024.4.1112
Browser: [all ]
The horizontal space between all OrgChart nodes on the same level is one and the same and it is equal to the horizontal space needed to show the child nodes of the parent with most child nodes. It is represented by the red squares on the image below. This results in excessive empty horizontal space between nodes with no child nodes or no visible child nodes.
This may be observed on the following Dojo runner. Currently the OrgChart has empty space between the first level nodes, and also there is empty space after the last node:
Suggested behavior:
There is no empty horizontal space between nodes on the same level - highlighted in yellow on the image above. In the above scenario, there should be no empty space between the first level's second and third node and no space after the third node, which may be observed, when the first node has no expanded child node:
In the OData v4 transport, batch submit treats a top-level HTTP 200 response as success, even when one or more operations fail. This is due to how the changesets function.
The parseBatchResponse function, which is called by the success callback belonging to the submit function of your OData v4 transport, as well as further processing in the same success callback. No attempt is made at handling anything other than responses having status codes [200... 299].
Please enhance batch handling so inner change set failures trigger explicit client error handling.
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".
Add grouping option to the TaskBoard - multiple rows showing rows for separate projects/initiatives and cards with related tasks for each one.
The row idea is seen at https://dhtmlx.com/docs/products/dhtmlxKanban/.
If a Popup is open and you click a Menu item, the Menu prevents the Popup from closing automatically.
The Menu prevents the Popup from closing
The Popup should close when the Menu item is clicked.
User want to drag the series point as well as series line(whole series line) in any direction, so the user can move the series where he want, please refer the below URL, where user can move the series point in vertical direction only, likewise the user want to drag the series point as well as series line in any direction, so he can set the threshold limit where he want by using the custom series and analysis the chart against his threshold limit http://jsfiddle.net/SpaceDog/QsKaJ/1/
Hi!
I have noticed the following behavior of the Kendo-UI MultiSelect widget (reproducible in this DOJO):
-> 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.
If the ColorPicker tools in the Editor are configured to render a gradient, you cannot type in the HEX/RGB inputs.
The inputs are not selectable and you cannot type in them.
The inputs should be selectable so that you can type in them.
In the Spreadsheet, when users scroll horizontally to columns that are not initially visible, then activate Freeze Panes, the Spreadsheet scrollbar behave incorrectly
When Freeze Panes is activated after horizontal scrolling:
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.
Hi!
I am using the Kendo-UI Diagram widget to display relationships between items, that cannot be changed directly. I.e. I do not want users to be able to modify the diagram on their own. Unfortunately, I was not able to completely prevent modification of the diagram via its options.
For instance, I have set editable.remove to false. This prevents removing items already present at the widget's creation time, but it does not prevent removing items added later via diagram.addShape().
There are also several keyboard shortcuts like Ctrl+C (copy), Ctrl+V (paste), Ctrl+X (cut) and Ctrl+D (duplicate) that I would like to turn off.
The only solution I have found so far is blocking the corresponding keyboard events and preventing their default behavior, but this seems more like a hack than a solution.
What do you suggest?
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);
},