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.

 

 

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.

 

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

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).

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:

 

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

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.

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? 

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

I am using KendoReact 10.2 and I am getting several warnings about deprecated Sass methods and syntax including one that is causing an error in the browser and blocks rendering. I used the sass-migrator to try to migrate these methods.

Please upgrade KendoReact so it can work with the latest Vite, React and scss/sass packages without deprecation warnings and errors.
Also fix the React version dropdown in this feedback form. It doesn't show React 19 as an option.

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?

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. 

in latest v9.3.1 it appears GridFilterCell isn't passing properties shaped as 'isRequired' on DatePicker popupSettings 

this does seem to be a regression because i just recently noticed it in latest upgrade which we need for other bug fixes.

i pursued patching myself by populating animate in GridFilterCell.mjs which seemed to work but then i got warning for the next required property "appendTo". however, populating appendTo yields warning "Warning: Failed prop type: Invalid prop `appendTo` supplied to `Kendo React Popup`. Validation failed." so it's not easily reconcilable that way... therefore i tried removing isRequired on all 3 DatePicker popupSettings properties which of course avoided warnings and i didn't see any negative side effects.

here is a codesandbox repro minimally tweaked to include a date field from kendo grid's "getting started" demo: https://codesandbox.io/p/sandbox/cool-sanne-d4tp85

admittedly this is just a warning but it does create unnecessary noise in browser debug which detracts from issues truly requiring attention during development.

screenshot with the warning from that demo repro:

When I change the width of the component, I expect that the state of the buttons (active/locked) will change depending on the scroll position, but this does not happen. For example, if the component did not scroll and both buttons are locked, then when the width is reduced, they will also remain locked. I think this is a mistake. Is there a way around this problem?

Test Environment:

OS: Windows_11

Environment Details:
OS: Windows11 version 21H2 (OS build 22000.856)
Edge Browser version: 104.0.1293.47

Repro steps:
1. Open Code Pen: https://codepen.io/m1mrt/pen/VwXjEzJ page in Edge Browser.2. Run Axe dev tools3. Observe an issue that select element has an accessible name.

Actual Result:Select element does not have an accessible name.

Hi thanks. When resizing a column the page skips in Edge. Please see attached video. KendoReact.