Unplanned
Last Updated: 26 May 2025 09:56 by Bridge24

When the workbook is exported to Excel, it is currently not possible to display the progress for example, in percentage of exported data. 

You are returning a "jquery promise", you can call the ".notify" function while the process is running and tell us that you are at step X of Y, when running these settimeout.

https://dojo.telerik.com/mHMUMjpg/6  

So, we can display a nice progressbar, instead of just a "loading animation" that doesn't tell if the process is really running. In some cases, it can take between 30 and 60 seconds, so the user think that the app is doing nothing!
Declined
Last Updated: 09 Jun 2025 07:26 by ADMIN
Created by: JEAN CHARLES
Comments: 3
Category: Kendo UI for jQuery
Type: Bug Report
0

Hi team, 

I think there is a bug in the dependency detection.

In the attached "config_buged.js" i have chosen some components. The component "chiplist" was partially checked due to dependency.

When lunching my application I got the error :

Message: e(...).kendoChipList is not a function
    at init._createList (kendo.custom.min.js:91:8505)
    at new init (kendo.custom.min.js:91:3218)
    at init._attachGroupable (kendo.custom.min.js:133:96797)
    at init._groupable (kendo.custom.min.js:133:96348)
    at init._continueInit (kendo.custom.min.js:133:33864)
    at new init (kendo.custom.min.js:133:33735)
    at HTMLDivElement.<anonymous> (kendo.custom.min.js:1:42737)
    at jQuery.each (jquery-3.1.1.js:368:19)
    at jQuery.fn.init.each (jquery-3.1.1.js:157:17)
    at e.fn.<computed> [as kendoGrid] (kendo.custom.min.js:1:42713)

 

I was forced to totaly check the "chipList" component as seen in the attached file config.json

 

Duplicated
Last Updated: 15 Jul 2025 07:49 by ADMIN
Created by: Karl
Comments: 1
Category: Kendo UI for jQuery
Type: Feature Request
0

Views - Month - numberOfWeeks (set to 6 weeks), do not need to see previous or next month week.  Only show days of the selected month.

This is OK:

This is not, unnecessary week of Aug 03.  The extra week adds to a busy calendar clutter.

 

 

Completed
Last Updated: 31 Jul 2025 10:28 by ADMIN
Release 2025 Q3 (Aug)

Hello

Starting from version 2025.2.520:
Kendo Grid with NumericTextBox cell editor and "navigatable: true" exit edit cell state on double click/hold to select number inside editor.
Earlier versions did not have this issue.

Scenario:

Inside cell with NumericTextBox editor trying to select value without exit from edit cell state.
On click cell, that already in edit mode, switch to read mode (NumericTextBox disappears) 

Desirable behavior:
Copy and paste to cell without exit and enter again in edit cell state.
Select all value without loosing editing cell state. 

Dojo

Unplanned
Last Updated: 26 Aug 2025 08:37 by ADMIN
Created by: Philip
Comments: 1
Category: Kendo UI for jQuery
Type: Feature Request
0

When a pager control uses responsive mode, but renders initially as hidden, the control fails to render properly.

The control should render to the appropriate responsive mode regardless of whether the control is visible or not when it is initially rendered.

Unplanned
Last Updated: 04 Sep 2025 13:53 by Andy F.
Created by: Andy F.
Comments: 0
Category: Kendo UI for jQuery
Type: Bug Report
0

Bug report

Currenlty, styles/font-icons/index.css has this line at the bottom:

/*# sourceMappingURL=index.css.map */

But the map file is not part of the distribution files, so it's causing the browser to throw an additional request for the map file.

Currenlty, the index.css.map is present in the node_modules/@progress/kendo-font-icons/dist/index.css :

Image

But is not part of the Kendo jQuery distribution.

Expected/desired behavior

The distribution should be revised and the map file should be copied.

Environment

  • Kendo UI version: 2025.3.825
  • Browser: [all ]
Declined
Last Updated: 24 Sep 2025 13:55 by ADMIN

We have a column in our grid bound to a complex JSON object. When a different column's value is changed, we need to change the nested properties in the complex JSON object.

To do this, in the grid's Save event, we are calling model.set("theComplexObject.NestedProperty", newValue). However, doing this does not automatically update the UI for that row's cell. Furthermore, it never seems to mark the column dirty. Manually calling grid.refresh() will fix the issue, but the grid we are working on has a lot of columns and it adds a performance hit.

This approach works for all of our other columns that do NOT use complex objects. They correctly show the dirty flag and new model value after the save operation completes.

Below is a Dojo example with the save event wired up and a complex name column. It's worth mentioning that the dirty flag also doesn't appear to be working on the eye color column. This may be another bug introduced in a newer version of Kendo.

https://dojo.telerik.com/ZHkxwJee

  • Change the age for a column and click off the cell. The eyeColor updates, but the name does not. The dirty flag gets put in the first cell for some reason (this happens when updating the second row too... it adds the dirty flag to the first cell in the first row).
  • Enabling the currently commented line that does e.sender.refresh() will fix the display issues, but the dirty flag still doesn't show for the name column.
Unplanned
Last Updated: 13 Oct 2025 06:35 by ADMIN

We have noticed a serious performance issue in the TreeList control which I have confirmed in the latest version in this Dojo: https://dojo.telerik.com/aNuKanAG.  This Dojo is a based on the TreeList in-cell editing demo from your website.

  1. Open the Dojo link I provided and Run it.
  2. Open your browser DevTools console so you can see console.log messages.
  3. Navigate to a leaf node of the tree if it isn't already open by default; ex: Daryl -> Guy -> Buffy -> Hyacinth
  4. Click in and out of an editable cell; ex: Ext
  5. Observe the DevTools console where you will see that the 'rendered XXX' text has been written for EVERY CELL in the entire tree.
  6. Expand/collapse the closest parent group
  7. Again, observe that EVERY CELL has been re-rendered

I was trying to figure out if there was any good reason for this.  In the Dojo above all data are nested under a single parent.  So, I created another Dojo but this time there are two  separate parent groups: https://dojo.telerik.com/OcEmAgIz.  This Dojo is based on the Binding to local data demo from your website.

  1. Open the Dojo link and Run it.
  2. Clear the DevTools console so you can see a clean display of results for the next action.
  3. Expand and collapse a child group of Daryl Sweeney.
  4. Observe the console log results: you will see that Dan Sweeney was also re-rendered.

The problem here is that these re-renders are very expensive.  Imagine if the call to console.log was instead something else that might need a bit of computation time to complete.

The simple act of expanding and collapsing a group from an unrelated part of the tree, or simply opening and closing an editable cell should not result in the entire tree being re-rendered.  This is a serious performance issue, and seems completely unnecessary.

 

What I have demonstrated in the Dojos I created is that Kendo is re-rendering the ENTIRE structure. The goal of this feature would be to rerender only the specific cells of the treelist that have been impacted by an edit. 


Unplanned
Last Updated: 28 Oct 2025 14:17 by Anthony
Created by: Anthony
Comments: 0
Category: Kendo UI for jQuery
Type: Bug Report
0

Bug report

When using the raw JavaScript files from the src\src\dist\raw-js folder (included directly via <script> tags), the Kendo UI version (kendo.version) always returns 0.0.0, and the package metadata in kendo.all.js has the version field hardcoded to 0.0.0.

Reproduction of the problem

1. Download Kendo UI for jQuery commercial distribution.
2. Use the files from the following path:
`src\src\dist\raw-js\`

3. Include kendo.all.js (and other scripts) directly in an HTML page using <script> tags.
4. Include a valid license key using:

`KendoLicensing.setScriptKey("your-license-key");`
5. Run the application and inspect the console.

Call: console.log(kendo.version);

Result: The version displayed is "0.0.0".

 

Current behavior

kendo.version returns "0.0.0".

_parsedPackageMetadata in kendo.all.js shows:

version: '0.0.0'


Expected/desired behavior

The kendo.version property should correctly reflect the actual build version (2025.3.1002 in this case).

The PACKAGE_METADATA placeholder should be replaced during the build or distribution process, even in the raw-js folder outputs.


Environment
Kendo UI version: 2025.3.1002
Browser: [all ]