Completed
Last Updated: 29 May 2026 14:27 by ADMIN
Created by: Owen
Comments: 4
Category: KendoReact
Type: Bug Report
6

When typing into a date picker and trying to type Feb 29th, 2024 (or any other leap year ofc) the date is updated incorrectly by the kendo date picker validation. As the user types the year their previous entry of 29 is updated to 28. This should update check should probably not occur until the user is done updating the input. If there is some fix or workaround we can do on our end to resolve this issue please let us know

Here's a video of the bug in our application

However, I was also able to reproduce the exact same behavior even in the documentation:

Completed
Last Updated: 29 May 2026 14:24 by ADMIN
Release 2025 Q4 (Nov)

Hi! 

I have noticed that keyboard navigation doesn't work in the filter editor components inside the Filter component

Reproduction:

  1. Open https://stackblitz.com/edit/react-rvwjsm?file=index.html
  2. Choose "name" or "price" from the first dropdown
  3. Type anything in the input field
  4. Try to change the cursor position in the field using arrow keys - doesn't work

 Is there a way to enable it or go around it? 

Completed
Last Updated: 29 May 2026 14:14 by ADMIN
Created by: Daniel
Comments: 8
Category: KendoReact
Type: Bug Report
1

Issue 1:

I've implemented insert table tool in the editor and I'm setting some states on editor blur. The bug appears when the editor is focused and I try to add a table. When I select the rows and cols from the dropdown  and click to insert the table the editor blur is called my setStates are called and somehow the table insertion doesn't happen. In order to add the table I should not focus the editor and I have to click on the insert table button and select again the cols and rows.

Issue 2:

In the same editor I've added tableResizing plugin. The bug appears when I already have a table in the editor and open the insert table dropdown to add a new one. In that moment when the dropdown is still opened I hover over some of the already inserted table cells borders the insert table dropdown is closed.

Issue 3:

When the editor is controlled we have undefined as initial value and then we type something or try to add table for example the editor crashes and throw an error `Uncaught RangeError: Applying a mismatched transaction`. Even though the value type allows undefined EditorProps.value?: string | Node | undefined. It works fine though if the initial value is empty string.

 

Package
"@progress/kendo-react-editor":"^5.11.0 | 5.12.0"

Minimal reproduction
I'm providing an vite + react + ts project. Steps to run the project:
npm install
npm run dev

It's reproducible in the provided examples in StackBlitz from Kendo, but the editor packages are not always resolved with turbo package manager. I guess it's the same issue as https://github.com/telerik/kendo-react/issues/1530

 

 

Completed
Last Updated: 29 May 2026 14:06 by ADMIN

To demonstrate:

1. Open your simplest interactivity/selection demo, which is not grouped, in StackBlitz. See: https://www.telerik.com/kendo-react-ui/components/grid/interactivity/selection/

2. Add the Grid's group prop. To demonstrate the bug nothing else needs changed

<Grid group={[]} ...

3. Run demo, scroll down and pick a row.

4. Observe the grid scrolls to the top and you cannot see your selected row unless you scroll back.

Unplanned
Last Updated: 29 May 2026 14:01 by ADMIN
Scheduled for Q2 2025 (May)
Created by: Speedy
Comments: 2
Category: KendoReact
Type: Bug Report
0
We have recently added the scrollable prop to our tabStrip component but we are noticing that now on the active tabs there is a line, which is not show when not using the scrollable property. Is there anyway to remove this line? It makes it more difficult in terms of affordance and UX to see that this element is the active tab when there is this line. It somehow breaks the connection between the tab and the content. 


Any help would be appreciated. 
Completed
Last Updated: 29 May 2026 13:59 by ADMIN
Release 2025 Q4 (Nov)
Created by: Maria
Comments: 2
Category: KendoReact
Type: Bug Report
0

Hi,

The first render of a DatePicker component with an onOpen prop throws an error: Unknown event handler property `onOpen`. It will be ignored.

Reproduction:

1. Open https://stackblitz.com/edit/react-xje2zdjc?file=app%2Fapp.tsx

2. The error will appear in the console

Expected behavior:

No errors in the console

Completed
Last Updated: 29 May 2026 13:58 by ADMIN

The examples from https://www.telerik.com/kendo-react-ui/components/intl/i18n/loading-data work with cldr* packages up to version 47.0.0. The Current version 48.0.0 causes an error:

Error in /turbo_modules/@progress/kendo-intl@3.1.2/dist/npm/main.js (759:20)

Cannot read properties of undefined (reading 'replace')

 

Completed
Last Updated: 29 May 2026 13:55 by ADMIN
Release 2026 Q1 (Feb)
Created by: Jie
Comments: 2
Category: KendoReact
Type: Bug Report
1

Please see the example - https://codesandbox.io/p/sandbox/silly-wind-tpfg8n

When column "Unit Price" is locked, while moving the horizontal scroll bar, the group header is sticky (expected behavior), but the group footer is not sticky (wrong behavior).

 

Completed
Last Updated: 29 May 2026 13:53 by ADMIN
Created by: Peter
Comments: 4
Category: TimePicker
Type: Bug Report
0

I'm submitting a...

  • Bug report

Current behavior

Timepicker component in adaptive mode behaves differently in version 11.0.0 (and above) compared to version 10.0.0 (and above):

  • "Set" button sets value but does not close popup - one more click needed
  • "NOW" button scrolls to current time, but does neither set value nor close the popup - two more clicks needed
  • in the top right corner there is a button with check icon which does the only thing - closes the popup (the same as "Close" button) - it is confusing

Expected behavior

We would expect the same behavior as in the 10.0.0:

  • "Set" button sets value and closes the popup
  • "NOW" button scrolls to current time, sets value and closes the popup
  • there are no two buttons with the same functionality

Minimal reproduction of the problem with instructions

  1. Please run following link: https://stackblitz.com/edit/react-j3smansk?file=app%2Fapp.tsx,package.json and adjust app container width so that the timepicker popup is rendered in the bottom half of the screen, allowing both the popup and the editor to be visible at the same time. 
  2. Repeat previous step for following link: https://stackblitz.com/edit/react-ukfuqrdy?file=package.json,app%2Fapp.tsx
  3. As you can see in "app.tsx" examples are very the same (taken from https://www.telerik.com/kendo-react-ui/components/dateinputs/timepicker/adaptive-rendering), only versions of kendo-react components in "package.json" are different
  4. Observe situations described in Current behavior and Expected behavior sections

What is the motivation or use case for changing the behavior?

We would like to upgrade to 11.0.0 but we do not like this behaviour because it is disturbing, confusing and requires more clicks (time) to work with it.

Environment

Browser:

  • Chrome (desktop) version 138.0.7204.50 (Official build) (64-bit)
  • Firefox version 140.0 (64-bit)
  • Edge Version 137.0.3296.93 (Official build) (64-bit)

System:

  • TypeScript version: KendoReact demos page version
  • Node version: KendoReact demos page version
  • Platform: Windows 10

Best regards,

Peter


Completed
Last Updated: 29 May 2026 13:52 by ADMIN
Created by: Hubert
Comments: 2
Category: Window
Type: Bug Report
0

When clicking on a resize handle (without dragging), the window unexpectedly shrinks.

Steps to reproduce:

  1. Open a Window component
  2. Click on any resize handle without dragging

Expected behavior: The window size remains unchanged when clicking a resize handle without dragging.

Actual behavior: The window shrinks.

Reproducible on the demo page: https://www.telerik.com/kendo-react-ui/components/dialogs/window

Completed
Last Updated: 29 May 2026 13:51 by ADMIN
Release 2026 Q2
Created by: Maria
Comments: 2
Category: KendoReact
Type: Bug Report
0

Hi, 

After pasting a value into the input box of the DatePicker I am then unable to clear it. The value of the DatePicker is correctly set to null, but the value displayed in the input box is unchanged.

Reproduction steps:

1. Open the grid filtering demo,

2. Copy any of the date values from the grid, e.g. 9/20/1996, and paste it into the "First Ordered On" filter,

3. Clear the filter using the clear button.

Result:

The value remains in the input box.

Expected behaviour:

The value should not be visible in the input box.

 

 

Completed
Last Updated: 29 May 2026 13:50 by ADMIN
Release 2026 Q2
Created by: Peter
Comments: 2
Category: TimePicker
Type: Bug Report
0

I'm submitting a...

  • Bug report

Current behavior

Timepicker components now button in certain situations does not scroll timeselector to current time in adaptive mode.

Expected behavior

We would expect the now button scrolls to current time in all situations, also in adaptive mode .

Minimal reproduction of the problem with instructions

  1. Please run following link: https://www.telerik.com/kendo-react-ui/components/dateinputs/timepicker/adaptive-rendering
  2. Clear timepicker value, there should be "hour:minute PM" in input
  3. Switch to tablet (or mobile) view
  4. Open time selector, it should be positioned to 12:00 AM, because it is min value
  5. Scroll AM/PM selector to PM
  6. Press NOW button
  7. Observe that timeselector did not scrolled to current time (if yes, only by huge accident)

What is the motivation or use case for changing the behavior?

It is obviously buggy behavior, we would like to use now button, but it has to work correctly.

Environment

Browser:

  • Chrome (desktop) version 144.0.7559.133 (Official build) (64-bit)
  • Firefox version 147.0.3 (64-bit)
  • Edge Version 144.0.3719.115 (Official build) (64-bit) 

System:

  • TypeScript version: KendoReact demos page version
  • Node version: KendoReact demos page version
  • Platform: Windows 10

Best regards,

Peter


Need More Info
Last Updated: 20 May 2026 14:19 by ADMIN
Test Environment:
OS: Windows 11 Version 25H2 (OS Build 26200.8390)
Browsers: Edge (Version 148.0.3967.70), Chrome (Version 148.0.7778.168)
Screen Reader: NVDA (2026.1), JAWS (2026.2603.86), Narrator

User Impact:
Screen reader users are getting impacted because the focus moves in an unexpected order after activating the combo box. This makes it hard to understand where they are on the screen and can cause confusion while navigating.

Pre-Requisites:
  1. Connect to 'MSFT AzVPN-Manual' VPN.
  2. Turn on Screen Readers:
    NVDA: Ctrl + Alt + N
    JAWS: Ctrl + Alt + J
    Narrator: Ctrl + win + Enter 
  3. Verbosity:
    NVDA: Default
    JAWS: Beginner, Highest
    Narrator: Default

Repro Steps:
  1. Open the URL: https://agoradev-ppe.azurewebsites.net/home?dashboard-id=RnRToolsHomePage in edge/chrome browser in windows.
  2. Agora Home page will open.
  3. Press tab key to navigate to the 'Save As' control and activate it.
  4. 'Save As' dialog will open.
  5. Press tab key to reach to the 'Save to workspace' combo box and activate it using enter key.
  6. Verify whether screen reader focus order is incorrect after activating the 'Workspace to be Saved As in' combo box or not.

Actual Result:
After activating the “Workspace to be Saved As in” combo box, keyboard focus moves to the search edit field, while the screen reader focus shifts to the /user control, causing a mismatch in focus.

Refer Attachment:
  1. Screen Reader focus order is incorrect after activating the 'Save to workspace' combo box in windows.png
  2. Screen Reader focus order is incorrect after activating the 'Save to workspace' combo box in windows.mp4

Expected Result:
After activating the combo box, both keyboard focus and screen reader focus should remain in sync and move to the search edit field in a proper sequence.
Need More Info
Last Updated: 20 May 2026 14:18 by ADMIN
Test Environment:
OS: Windows 11 Version 25H2 (OS Build 26200.8039)
Browser: Edge (Version 146.0.3856.84), Chrome (Version 146.0.7680.165)
Screen Reader: NVDA (2025.3.3), JAWS (2026.2603.86), Narrator

User Impact:
Screen reader users are getting impacted as they are unable to hear the names of the colors available in the Font Color dropdown, making it difficult for them to select the desired color independently.

Pre-Requisites:
  1. Connect to 'MSFT AzVPN-Manual' VPN.
  2. Turn on Screen Readers:
    NVDA: Ctrl + Alt + N
    JAWS: Ctrl + Alt + J
    Narrator: Ctrl + win + Enter 
  3. Verbosity:
    NVDA: Default
    JAWS: Beginner, Highest
    Narrator: Default

Repro Steps:
  1. Open the URL: https://agoradev-ppe.azurewebsites.net/home?dashboard-id=RnRToolsHomePage in edge/chrome browser in windows.
  2. Agora Home page will open.
  3. Press tab key to navigate to the 'Add a widget' control and activate it.
  4. Press tab key to navigate to the 'Table' control and activate it.
  5. 'Create Table' dialog will open.
  6. Press tab key to reach to the 'Font' dropdown control and activate it using enter key.
  7. Font color options will appear.
  8. Verify whether screen reader announces the name for the colors Present in Font dropdown control in windows or not.

Actual Result:
Screen reader does not announce the name for the colors Present in Font dropdown control in windows.
Screen Reader announces as '#ffffff row 1 column 1'

Refer Attachment:
  1. Screen reader does not announce the name for the colors Present in Font dropdown control in windows.png
  2. Screen reader does not announce the name for the colors Present in Font dropdown control in windows.mp4

Expected Result:
Screen reader should announce the name for the colors Present in Font dropdown control in windows.
Screen Reader announces as '#ffffff row 1 column 1 White'
Unplanned
Last Updated: 11 May 2026 14:17 by ADMIN
Scheduled for 2026 Q2
Created by: Alex
Comments: 1
Category: KendoReact
Type: Bug Report
0

I have noticed that whenever you want to upload multiple photos at once, using this React Upload Component & Events - KendoReact Docs & Demos (telerik.com) component the previews of the images uploaded bounce/ shake around. I've tried this on multiple browsers and they all have the same bouncing effect for the image previews. For a single photo it doesn't do it but once multiple images are added, it will do it.

 

Completed
Last Updated: 05 May 2026 13:28 by ADMIN

Hello

Localization messages for ColorPicker popup Apply/Cancel are missed.

Option to hide does not work flatColorPickerSettings={{showButtons: false}}

 

stackblitz

 
Completed
Last Updated: 11 Feb 2026 16:36 by ADMIN
I am using conditional rendering to render a custom editor for the resources in the Scheduler. Even if there is no resource editor the label still renders. 
Unplanned
Last Updated: 13 Jan 2026 09:37 by ADMIN
Test Environment: 
OS: Windows 11 Version 24H2 (OS build 26120.2705)
Browser Edge Version 132.0.2957.55

URL: https://codesandbox.io/p/sandbox/objective-blackburn-jvz3py

User Impact:

Keyboard dependent users will find it difficult to navigate as the focus order is not logical when navigating through the "Upload" controls of bar charts components.

Repro steps:
  1. Open URL: https://codesandbox.io/p/sandbox/objective-blackburn-jvz3py in the latest chrome browser.
  2. Code sandbox page will appear. 
  3. Press tab key from the top of the page to "https://jvz3py.csb.app/" edit field on right side to reach the Bar chart.
  4. Press tab key to move focus between bar charts and press arrow keys to navigate through the bar chart points.
  5. Verify on pressing tab keys whether the keyboard focus order is logical while navigating the "Upload" controls of Bar chart components.

Actual Result:
Keyboard focus order is not logical when navigating through the "Upload" controls of bar charts components in windows. Focus will not move to the 'Upload' button it will move to the next bar graph control.

Refer Attachment: Keyboard focus order is not logical when navigating through the Upload controls of bar charts components.mp4

Expected Result:
Keyboard focus order should be logical while navigating the "Upload" controls of Bar chart components in windows. Focus should move to the 'Upload' button.
Declined
Last Updated: 19 Dec 2025 10:41 by ADMIN
Created by: Hubert
Comments: 1
Category: KendoReact
Type: Bug Report
0

The Data Grid does not work properly with large datasets. In the example below with one million records, it is impossible to scroll to the bottom of the grid.

Firefox: Rows fail to render after scrolling past approximately 200,000 rows.

Chrome: Rows do render, but the skip parameter never exceeds 745,645 even when the scrollbar is at the bottom, preventing access to the remaining ~254,000 records.

This contradicts the documentation's claim that the grid "scales from hundreds to millions of records while maintaining a responsive user experience."

 

https://stackblitz.com/edit/react-aaxnyzxm?file=app%2Fapp.tsx

Need More Info
Last Updated: 21 Nov 2025 13:08 by ADMIN
Created by: Andrei
Comments: 10
Category: KendoReact
Type: Bug Report
0
We use "@progress/kendo-react-treelist": "^5.10.1" in our project. Trees are usually placed in flexible containers, and users can reduce their size to 0. At this point, we get an error when calling the tableRowsVirtualization function. I have attached a screenshot at the moment of debugging. You can see that the values of items[0] and lastItem are undefined when the container size approaches 0. I didn't prepare an example to reproduce the error, because I think it's pretty clear that an error occurs here. So the questions are: if this is a bug, is it fixed in the new versions of the package? If there is a possible error on our part or it has not been fixed in the new versions, then what should we do to solve the problem? Thanks
1 2 3 4 5 6