Bug report

Following the commands in the following article

https://www.telerik.com/kendo-jquery-ui/documentation/intro/installation/ecmascript

and the steps for version after February 2026 - https://www.telerik.com/kendo-jquery-ui/documentation/intro/installation/ecmascript

when running npm run scripts: custom command or npm run build: custom an error is thrown:

Error: spawn npx ENOENT

at ChildProcess._handle.onexit (node:internal/child_process:287:19)

at onErrorNT (node:internal/child_process:525:16)

at process.processTicksAndRejections (node:internal/process/task_queues:90:21)

Emitted 'error' event on ChildProcess instance at:

at ChildProcess._handle.onexit (node:internal/child_process:293:12)

at onErrorNT (node:internal/child_process:525:16)

at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {

Expected/desired behavior

A custom folder containing a custom script wth only the needed components should be created.

Environment

• Kendo/Telerik version: 2026.3.811
• Browser: [all ]

I am using the Kendo-UI Grid's resizeColumn method do change column widths programmatically (e.g., to distribute column widths by our own custom rules). I have noticed that doing so sometimes leads to unexpected results as demonstrated in this DOJO:

Assume a grid with two columns: one has a fixed size of 200px and the other has no explicit width set.

In the first example, we programmatically set the first column's width to 200px (which should not change anything since the column already is 200px wide. 

grid.resizeColumn(column, 200);

This works as expected.

In the second example, we programmatically set the first column's width first to 20px and then immediately to 200px. I would expect the final outcome to be the same, since the second column should compensate.

grid.resizeColumn(column, 20);
grid.resizeColumn(column, 200);

However, the second column does not shrink and the overall grid grows larger instead. Doing this repeatedly causes the columns to grow larger and larger over time.

Of course, this is a simplified example and I do not call resizeColumn() twice right after each other.

Bug report

Current behavior

Errors during build process:

(replace-metadata plugin) [SOURCEMAP_BROKEN] Sourcemap is likely to be incorrect: a plugin (replace-metadata) was used to transform files, but didn't generate a sourcemap for the transformation. Consult the plugin documentation for help: https://rolldown.rs/guide/troubleshooting#warning-sourcemap-is-likely-to-be-incorrect

Expected/desired behavior

There should be no errors

TicketID:

1716119

Bug report

Reproduction of the problem

Follow the stpes described in the link below:

https://www.telerik.com/kendo-jquery-ui/documentation/intro/installation/ecmascript#manually-building-the-source-code

Current behavior

When running the npm run build error appear Cannot find package 'glob' imported from …..\kendoui.for.jquery.2026.3.811.source\src\rolldown.config.mjs

Expected/desired behavior

There should be no error and the kendo scripts should be built as expected.

• Kendo/Telerik version: 2026.3.811
• Browser: [all ]

When unformatted multi-line content is pasted in an existing paragraph inside the Kendo Editor, the paragraph is removed and the pasted content is inserted in the body of the Editor.

Steps to reproduce:

• Open: https://dojo.telerik.com/osANirag/8
• Type in the content editable: "text row 1", hit ENTER, type "text row 2"
• Copy the content from the content editable.
• Paste the content in the first paragraph in the Kendo Editor

Result:

The pasted content replases the paragraph.

Expected Result:

The pasted content should be inserted in the paragraph.

Bug report

The kendo.culture.nb-NO.min.js file contains some unwanted characters: "Â".

Reproduction of the problem

See Ticket ID: 1486493 for more details.

The unminified file looks correctly: https://github.com/telerik/kendo-ui-core/blob/master/src/cultures/kendo.culture.nb-NO.js

Current behavior

Expected/desired behavior

Environment

• Kendo UI version: 2020.3.915
• jQuery version: x.y
• Browser: [all]

Bug report

ContextMenu allows having focused and hovered items simultaneously.

Reproduction of the problem

Current behavior

There is an item marked with 'k-hover' class and an item marked with 'k-focus' class.

Expected/desired behavior

It is supposed to have a single active item in the ContextMenu.

Environment

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

 My recurrence rule is: FREQ=MONTHLY;COUNT=2;INTERVAL=1;BYSETPOS=2;BYDAY=WE;WKST=SU. This event falls on the second Wednesday of the month for two months in a row. When I edit the event, the wrong option is picked. Note in the screenshot attached we are on 11/09/2022 which is the second Wednesday. And the scheduler correctly shows this event. But the edit window sets the properties wrong. I am using a custom template for the edit window, however the recurrence editor portion is unmodified.

 I was able to fix this in the Kendo.all.js file directly. The highlighted lines below were added. When I publish this for customers I use the Kendo custom download tool to get a minified script of only what I need. I then need to carefully port this change using Notepad++. This makes it tough to update versions which is why I am a few versions back.

There is an issue regarding text inputs in forms, when clicking the label (in a chrome emulator e.g. https://demos.telerik.com/kendo-ui/m/index#mobile-forms/index) or when clicking the form (on android).

The input and label move to the left edge.

When a kendoContextMenu is applied to a combobox (html tag select) you are not able to show the select options by tapping it. The behaviour is on mobile browser only (tested iPad and Google Chrome developer tools with device toolbar enabled).

I reproduced the issue in telerik dojo, here is the code.

<!DOCTYPE html>
<html>
<head>
    <base href="https://demos.telerik.com/kendo-ui/menu/context-menu">
    <style>html { font-size: 14px; font-family: Arial, Helvetica, sans-serif; }</style>
    <title></title>
    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2021.1.330/styles/kendo.common-bootstrap.min.css" />
    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2021.1.330/styles/kendo.bootstrap.min.css" />
    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2021.1.330/styles/kendo.bootstrap.mobile.min.css" />

    <script src="https://kendo.cdn.telerik.com/2021.1.330/js/jquery.min.js"></script>
    
    
    <script src="https://kendo.cdn.telerik.com/2021.1.330/js/kendo.all.min.js"></script>
    
    

</head>
<body>
    <div id="example">
      <select>
        <option>Opzione 1</option>
        <option>Opzione 2</option>
        <option>Opzione 3</option>
      </select>
      
    <ul id="menu">
        <li>
            <img src="../content/web/toolbar/reply.png" /> Reply
        </li>
    </ul>
      
</div>
<script>
    $(document).ready(function() {
        setTimeout(function () {
            var initMenu = function () {
                menu = $("#menu").kendoContextMenu({
                    target: "select",
                    select: function(e) {
                        // Do something on select
                    }
                });
            };

            initMenu();
        }, 0);
    });
</script>

</body>
</html>

Hi,

I've notice an issue with Scheduler: the height for group slot is not correct calculated and items goes down to the next group slot.

Scheduler :

   - group vertical after a field

   - type of scheduler: "timelineWeek" or "timelineMonth"

   - items of the group have same start date and their number are bigger then 20.  

kendo ui version: 2020.1.219. Same issue with 2021.1.119

----------------------------------------------------------------------------------------------------------------------

I've created a dojo as example:  https://dojo.telerik.com/EHeNigIQ  .   Also, you can see the issue into the picture bellow.

You can modify the variable  "rows = 30;"  and you will see more items that goes wrong into the other group slot.

On https://demos.telerik.com/kendo-ui?_ga=2.149841974.1082962146.1579102350-1080570292.1579102350 , all links in the "Sample Applications" section return 404 (for example https://demos.telerik.com/bootstrap/ )

Removing all URL params helps.

Any URL param ( https://demos.telerik.com/kendo-ui?x=1 ) reproduces the issue.

The following typings are missing in @types/kendo-ui version 2019.3.0

1. kendo.data.TreeListModel has no parentIdField
2. kendo.ooxml.WorkbookSheetRow has no property "type"
3. kendo.ui.PanelBar has no dataSource
4. kendo.ui.DatePicker has no dateView (it's used in https://docs.telerik.com/kendo-ui/knowledge-base/datepicker-show-quarterly-frequency  )
5. kendo.ui.EditorEvent has no keyCode
6. kendo doesn't expose kendo.wheelDeltaY()
7. kendo.data doesn't expose "binders" (filed at https://github.com/telerik/kendo-ui-core/issues/4049 )
   

In a grid with virtualization, when just normally scrolling down requests for the exact same data are often sent multiple times after each other. The reason for this is probably that the grid sends an asynchronous request for example Top 100, Skip 200 and then does not keep track of that it is still waiting for a reply for this request, before asking for the same data a short period later. 

Commonly requests for the same data is made 2 or 3 or more times after each other, causing performance problem at the server side and in many cases unnecessary calls to the database. Fixing this should lower the number of requests for data to the server considerably, maybe with a factor two or more with just normal grid operation when the user is just scrolling down to view more data in the grid.  

To demonstrate the problem, open a copy of the virtualization grid demo, for example here:

https://dojo.telerik.com/iXijoyaY

Open the Developer Tools and just observe which network requests are sent to the server. Just scroll down in any way and observe that very often the exact same request is made. A request for the same data has the same Top and Skip values in the parameters sent the server. You can see the servers reply is exactly the same JSON data multiple times after each other.

Solving this performance problem almost completely would seemingly be to in a variable just keep track of the "Latest request" sent, since the problem happens mostly just with normal scrolling in one direction with request sent after each other. So one would need to keep track of that a call for Top 100, Skip 200 has been made, and if the program wants to request the exact same data again, just wait for a reply for the first request, instead of sending a new one. (If needed, send a new request only after a specific timeout for a reply for the first one).

A more thorough solution would be to have a data structure to keep track of the Top and Skip tuples for all the calls to the server that has not yet have had a reply from the server, and not repeat those exact same calls again if still waiting for a reply for the first request.

Bug report

When a decimal number has 8 digits after the decimal separator and '#' is used for formatting the precision is lost and the number is rounded.

Reproduction of the problem

1. Open the Dojo example and check the result in the console

Current behavior

kendo.toString(0.00000015,"###.########" returns 0.0000002

Expected/desired behavior

The number should not be rounded and the precision should not be lost. The results should be the same with kendo.toString(0.00000015,"n8") and kendo.toString(0.00000015,"0.00000000")

Environment

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

Dojo example.

1. Resize the browser window so that its height is smaller than the DropDownTree's popup height.
2. Click the DropDownTree to open its popup.
3. The popup opens and then auto-closes

This is an error that took us an hour to figure out.

We are using the right-arrow icon as part of the content within a collapsible header to represent a state transition. (See image)

We found that the expand/collapse icon did not appear.

Further investigation reveals that if the header content contains a span with a class matching the regular expression k-i-arrow.* then the expand/collapse icon doesn't work. It could contain anything else, it was just that one class pattern that threw it.

See this example. https://dojo.telerik.com/EwAsaKAf/3

I also posted a forum message here: https://www.telerik.com/forums/expand-collapse-arrow-fails-to-appear-if-a-class-matching-a-certain-pattern-appears-anywhere-in-the-header   

This is clearly a bug, and one that I suspect can be fixed easily.

Hello!

Prior to 2024.2.514 (2024 Q2), the DateRangePicker would "force users first to select start and then end range regardless of the date input selected" [1,2]. However, with the latest 2024 Q2 release, clicking the End input on the DateRangePicker selects the range end.

I did not see this specifically mentioned in the release notes, https://www.telerik.com/support/whats-new/kendo-ui/release-history/kendo-ui-for-jquery-2024-2-514-(2024-q2), so I am reporting this as a bug.

Here is a basic Dojo to demonstrate: https://dojo.telerik.com/IWAbUpuV. You can see the previous behavior by changing the library to the previous version (2024.1.319).

References

1. https://feedback.telerik.com/kendo-jquery-ui/1449956-modifying-date-range-begin-end-values-exclusively-using-begin-end-inputs
2. https://feedback.telerik.com/kendo-jquery-ui/1582861-daterangepicker-selection-process-confuses-users-should-be-able-to-select-dates-independantly-for-from-and-to-range