Unplanned
Last Updated: 20 Oct 2026 14:51 by ADMIN

With the ArcGauge component, when you set the rangeLineCap to something other than 'butt' (ie:  round or square), the indicator does not line up with the tick lines.  This leads to misleading values.  Please look at this StackBlitz:

 

https://stackblitz.com/edit/react-itztql

 

This will show the comparison between round and butt rangeLineCaps. 

From the screenshot as well, the ArcGauge on the right looks like the value is greater than 0, resulting in the user being mislead on the result.

Unplanned
Last Updated: 20 Oct 2026 14:45 by ADMIN
Created by: Kavitha
Comments: 5
Category: Editor
Type: Bug Report
0
Repro-Steps:
  1. open answers.microsoft.com/en-us/msoffice/ using valid credentials.
  2. Navigate to any article link and hit enter.
  3. Select 'reply' button.
  4. Navigate to 'format' list and invoke it.
  5. Now Run the fast pass using Accessibility Insights for web and observe the failure 'aria input field name'.

Actual Result:
Aria input field doesn’t have an accessible name.

Control type is defined incorrectly as list item for combo box for 'format' combo box.

Expected Result:
Ensure every aria input field should have an accessible name.
Control type should be defined as combo box.

User Impact:
ARIA widget roles require additional attributes that describe the state of the widget. If a required attribute is not provided, the state of the widget will not be communicated to screen reader users.
Unplanned
Last Updated: 14 Aug 2026 07:27 by ADMIN
Created by: Hubert
Comments: 1
Category: DropDownList
Type: Bug Report
0

When filterable={true} is set, the filter input field does not respond to Home and End keys. The keys are swallowed and never reach the input element, making cursor navigation less convenient.

Steps to Reproduce:
- Render a DropDownList with filterable={true}
- Open the dropdown and type a string into the filter input
- Press Home, End, Shift+Home, or Shift+End

Expected: cursor moves to start/end of input; Shift+Home/Shift+End selects text
Actual: nothing happens in the input field

https://www.telerik.com/kendo-react-ui/components/dropdowns/dropdownlist/filtering

 

Unplanned
Last Updated: 28 Jul 2026 07:34 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.
Unplanned
Last Updated: 30 Sep 2025 12:02 by ADMIN

If TabStrip animation is set to false, TabStripTab content width is 100%. If TabStrip animation is set to true (default), TabStripTab content width depends on the content and TabStripTab.contentClassName has no impact on the width of the content.

We should not have to override css classes to set the TabStripTab content width to 100% with animation enabled. As a result we have disabled TabStrip animations everywhere.

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

Unplanned
Last Updated: 04 Jul 2025 09:02 by ADMIN
Created by: Hubert
Comments: 3
Category: Grid
Type: Bug Report
0

Hello,

there are numerous problems with navigating / scrolling on the DataGrid using keyboard keys.

Here is the test page:

https://stackblitz.com/edit/react-brdhufzd

 

1. Grid with navigatable=true:

- arrow keys - when you select a cell to be able to navigate and then  keep pressing down and then up, it's not posible to come back to the first record. You need to use the mouse.

- Page up/down keys work the other way round, also sometimes is not possible to come back to the first record, the scrollbar does not show the current position.

- It starts to work correctly after using the arrow keys and page up/down keys alternatively couple of times

2. Grid with navigatable=false:
- arrow,Page up/down keys and scrollbar work correctly

3. Grid with navigatable=true and nested inside Window:
- works the same way as not nested - the same problems occur

4. Grid with navigatable=false and nested inside Window:
- arrow keys move the window instead of navigating the grid
- Page up/down don't work at all



Unplanned
Last Updated: 01 May 2025 11:51 by ADMIN

Several months ago, I used this example to hide the default row detail expander, and implement my own custom expander:

https://www.telerik.com/kendo-react-ui/components/knowledge-base/custom-expand-collapse-column

As you can see, it seems that some upgrade along the way has broken the example, and it now shows two expander columns. This is also happening when i attempt to upgrade the version in my project. Can this be fixed, or is there a new workaround?

Unplanned
Last Updated: 16 Apr 2025 07:20 by Amit

Description

PivotGrid does can not export all the date to excel when the nodes are collapsed

Plan

KendoReact Free

Steps To Reproduce

https://www.telerik.com/kendo-react-ui/components/pivotgrid/excel
Configure a PivotGrid with multiple row and column fields, and at least one measure.

Expand only a few nodes manually.

Click the Export to Excel button.

The exported file contains only the visible/expanded rows/columns.

Screenshots or video

No response

Actual Behavior

It is not practical or user-friendly to expect users to manually expand every node (especially if data changes frequently).

Users expect complete data export based on the selected dimensions/measures and based on provided data source to generate pivot grid — not just what is visible.

Expected Behavior

Expected Behavior:
When clicking Export to Excel, PivotGrid the entire dataset should be exported in expanded format.

Browser

Chrome, All

Browser version

latest

OS type

MacOS

OS version

No response

Last working version of the KendoReact package (if regression).

No response

Unplanned
Last Updated: 31 Mar 2025 14:13 by ADMIN

We use data grids with virtual scrolling for inline editing a large number of records. However, when we want to add a new row to the grid it automatically resets the scroll position and doesn't even fire onPageChange event so the records you see do not correspond to the scroll position.

Check the following example (scroll to bottom, click anywhere on the table - this will add a new row - and observe the described problem):

https://stackblitz.com/edit/react-52zzvz?file=app%2Fapp.tsx%3AL78

Unplanned
Last Updated: 31 Mar 2025 08:11 by ADMIN

As per the subject. This can be observed in the following StackBlitz which is forked from the Telerik documentation on resizing with three small changes:

  • Remove style={{ height: '400px' }} from the Grid component in app.tsx
  • Remove height: 100%; from my-app style in index.html
  • Remove height: 100%; from html, body style in index.html

https://stackblitz.com/edit/react-vajzshwv?file=app%2Fapp.tsx,index.html

Logged as a bug because there is nothing in the documentation stating that a height for the Grid or Grid container must be set in order for this to work. If this is a documentation issue rather than a code issue, please advise the recommended approach for using the Grid resizable property.

Unplanned
Last Updated: 16 Oct 2024 12:30 by CompuMed

Setting the stage prop to "DEFAULT" does not update the Window component as expected:

const [stage, setStage] = React.useState<string>('DEFAULT');  

const handleStageChange = (e: WindowActionsEvent) => {
    setStage('DEFAULT');
  };

<Window
          stage={stage}
          onStageChange={handleStageChange}

Unplanned
Last Updated: 27 Sep 2024 05:02 by ADMIN

Setting the window position is not permanent.

How to reproduce:

  1. open https://stackblitz.com/edit/react-hyhjxg?file=app%2Fapp.tsx
  2. click 'move to corner' button
  3. click the window title bar
  4. the window changes its position to the previous one, but it should remain in place.

Chaging window stage also reverts previous position

 

 

Unplanned
Last Updated: 27 Sep 2024 04:52 by ADMIN

Hello,

We have recently upgraded our packages to version: "@progress/kendo-react-grid": "^6.1.0". While testing the new look and feel of the application we've noticed that the pagination is no longer working on several grids from the application. After investigating for a while, we have found the property that is causing the issue(rowHeight), please take a look at the Stackblitz example from below.

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

As you can see, in the example the pagination is not working. If we remove the property "rowHeight" from the grid the pagination is working again. We are not sure how these two are related but can you tell us what is going wrong and how we can fix it?

Thanks!

Unplanned
Last Updated: 19 Jun 2024 20:20 by ADMIN

Hi, Keyboard navigation using "page down" and "page up keys" doesn't work.

Here is a stackblitz where the problem can be reproduced: https://stackblitz.com/edit/react-q9n5fe?file=app%2Fmain.tsx
Reproduction steps:

  1. Click inside the grid
  2. Press "Page down" or "Page up" - doesn't work

It only works when:

  1. Click outside of the grid
  2. click on vertical scroll bar without selecting any grid cell.
  3. Press"Page down" or "Page up" - it works.

Best Regards

Hubert

Unplanned
Last Updated: 06 Jun 2024 08:08 by Brad

I'm submitting a...

  • Bug report

Current behavior

When importing Excel files that contain values with a currency formatting, the currency signs are not displayed correctly.
image

Expected behavior

When importing an Excel file, the data displayed in the Spreadsheet component should look the same way as in the imported document.

Minimal reproduction of the problem with instructions

  1. Download this SampleData.xlsx file
  2. Go to this example from the documentation
  3. Click on "File -> Folder Icon"
  4. In the popup select the downloaded file and import it

Environment

Package versions:
KendoReact 8.0.0

Unplanned
Last Updated: 11 Apr 2024 11:10 by ADMIN
Repro-Steps:
  1. open the given URL using valid credentials.
  2. Navigate to 'Reply' button and invoke it.
  3. Navigate to 'table' button and invoke it.
  4. Now, try to navigate to table cells to select the size of the table and observe

Actual Result:

After invoking 'table' button, user is unable to select the size of the table i.e, Keyboard focus is not going to 'Insert row and column cell components.

Tab index property is not defined.

 

Expected 
Control(s) must be accessible to keyboards and other assistive technology. Common causes of this problem include a) the element does not have a proper role assigned, b) the element needs tab-index="0" attribute to be focusable, or c) the component is not registering keypresses.  

User should be able to navigate to insert row and column cell components to select the size of the table.


User Impact 
When interactive components are not accessible, assistive technology users are blocked, which leads to everything from inaccessible content, features, and functionality, up to entire applications or sites. 

Unplanned
Last Updated: 25 Mar 2024 17:43 by ADMIN
Created by: Owen
Comments: 6
Category: DatePicker
Type: Bug Report
3

Hello,

We've been experiencing a weird behavior with the date picker element. We wanted to have an auto advancing cursor that moves from date -> month -> year without the user having to manually press the arrow keys.

We based our solution off this previous method in your JQuery element. However the React element has some buggy behavior when it comes to updating existing date values in the input that makes this method impossible. (the functionality works correctly in the JQuery version of the library, just not React)

When updating an existing value in the box from a single digit value (e.g. 01, 02, 03, 04, but not 10, 11, 12) instead of overwriting the existing value it appends the new number the user entered. For example, if a 01, is in the box and the user types 2 it becomes 12, when it should have become 02.

This can be especially confusing for the user when working with named dates (e.g. "Jan", "Feb",  "Dec", etc) since they do not see the numbers involved. If the user is updating Jan, and they press 2. It should update to Feb not Dec...

I've attached a GIF of the problem below as I've described

Unplanned
Last Updated: 28 Jul 2023 11:39 by ADMIN

Hi Team, 

There is some unexpected behavior when resizing events after switching the Scheduler to 'Show Full Day'. Take a look at my sandbox, you'll notice, its barely anything, let alone anything fancy.

Replicate:
1. Create a new event that starts at 8am.
2. Switch the view to 'Show Full Day'
3. Using the start time resize handle and drag it up, to start earlier. And you will notice the dragItem actually drags down, and when you release the handle, the event appears in the correct place

This will only happen on the first resize when switching to 'Show full day'. You can replicate it more by switching back and forth between full day and business hours.

Similar Scenarios include:
1. Placing the event to end at 8am, switching to business hours and back, then drag the end time down, the dragItem will be positioned to start at 8am, but say its 7am and you will see the rest.
2. Placing the event to overlap 8am, will yield both problems.

Again this only happens on the first resize after switching views, and I've only tested it in DayView, so it might affect WeekView as well. There appears to be no issue when events overlap the endWorkTime.

Thanks,
Grant

Unplanned
Last Updated: 27 Jul 2023 07:55 by ADMIN

https://stackblitz.com/edit/react-haejnu?file=app%2Fmain.tsx%3AL115

It is a common use case to provide Grid's dataItemKey property to make sure changes are properly reflected per documentation - https://www.telerik.com/kendo-react-ui/components/grid/api/GridProps/#toc-dataitemkey

However, when this accessor property is provided (usually a unique ID on all groups and items), Kendo uses it instead of its default auto-incremented `'ai' + absoluteIndex` key to index the <GridRow /> for each group's header and footer - giving them the same value and causing React to throw multiple warning about duplicate keys. This makes it unreliable to specify dataItemKey property when using the grouping feature with aggregate footers as it messes up with React's reconciliation mechanism.

Unplanned
Last Updated: 26 Jul 2023 14:02 by ADMIN
Created by: Joca
Comments: 1
Category: KendoReact
Type: Bug Report
2

There is an issue with ComboBox remote virtualization.  This is reproducible on https://www.telerik.com/kendo-react-ui/components/dropdowns/combobox/filtering/#toc-filtering-with-remote-data-and-virtualization

Scroll slowly till almost the end of the list. Pay attention to the name: Paula Parente

Notice that the name keeps repeating after scrolling as the scroll goes back and forth. You'll need to scroll a few times more before the scroll continues to load

other items.

 


1 2