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.

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:

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

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

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:

here's a simple repro project minimally tweaked from an original kendo demo:

https://codesandbox.io/p/sandbox/suspicious-lovelace-8nmzgj?file=%2Fpackage.json

just start dragging a column resize handle and you should see the "jitter" right away. in our experience, the jitter is so pronounced that resizing columns is no longer practically usable.

please note this bug is definitely related to putting the kendo grid inside of a css-grid, see that definition in the parent <div style>

as you may imagine, we use css-grid for our overall page layout which i believe is still modern best practice and we really hope you can fix this regression within that usage context.

note, the bug manifests regardless of the gridTemplateAreas or gridTemplateColumns, you can eliminate those entirely and it's still present.

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? 

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.

Hello,

We are encountering an issue with duplicate entries in our Kendo Grid with drag & drop functionality. When the grid is scrolled, clicking on any of the header cells multiple times results in the first entry being duplicated. This problem occurs on the example provided on your website as well: Kendo React Grid Row Reordering

Reproduction Steps:

1. Scroll down within the grid.
2. Click on any header cell multiple times.
3. Scroll back to the top of the grid.

You will notice that the first entry is duplicated multiple times. It appears that the reorder logic is being triggered when a header cell is pressed.

We are using version 6.1.0. Please refer to the attached video for a visual representation of the issue.

Thank you for your assistance.

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:

This is a bug on your documentation website.

Go to https://www.telerik.com/kendo-react-ui/components/grid/ for example to see that the side panel on the left is empty in an Edge browser. It flickers then it disappears.

It works fin in Chrome and Firefox. 

Hi team, 

Im my example (see here), I've added a 'name' attribute to the 'Persons' resource data, and changed the textField mapping to use the 'name' field, however the scheduler is still displaying the results of the 'text' attribute. 

Leading me to think that the scheduler is hardcoded to only look for the text attribute, because if its changed/removed, the scheudler does not display anything, regardless of what the 'textField' value is.

Please advise.

Thanks,
Grant

Environment (OS, Application, Versions)

Repro Steps

1. Open URL: Column Menu - Kendo React (telerik.com)
2. Navigate to context menu controls available on column headers of Basic usage table.
3. Verify if context menu is accessible using keyboard.

Actual Results

The 'context menu' controls available on the column headers under the basic usage table are not accessible using the keyboard.

Expected Results

The 'context menu' controls available on the column headers under the basic usage table should be accessible using the keyboard.

React Server Components allow the developer to mix the fast server-side rendering with the interactivity of client-side JavaScript. 

So far modern JS frameworks were explicitly operating on the client (with SSR being an optional feature). With server-components it's the opposite - RS Cs introduce a new mental model for building hybrid applications that leverage both the server and the client.

The main advantages of the React Server Components are that:

• Initial page load is faster;
• You can move the data fetching to the server;
• You can keep the large dependencies on the server;
• The client-side JavaScript bundle size is reduced;

Hi, when using the Kendo React Typography component like following:

<Typograpy.h1></Typograpy.h1>

compiler gives the following warning:

Imported JSX component h6 must be in PascalCase or SCREAMING_SNAKE_CASE                                                                       react/jsx-pascal-case

Hello,

when using the StrictMode we get an UncaughtError when using the PopupComponent. Fe. when using the Date/Time-Picker.

ERROR
Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.
    at checkForNestedUpdates (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:27287:11)
    at scheduleUpdateOnFiber (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:25470:3)
    at Object.enqueueSetState (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:14067:7)
    at Component.setState (webpack-internal:///./node_modules/react/cjs/react.development.js:355:16)
    at PopupWithoutContext.componentDidUpdate (webpack-internal:///./node_modules/@progress/kendo-react-popup/dist/es/PopupWithoutContext.js:285:18)
    at commitLayoutEffectOnFiber (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:23328:30)
    at commitLayoutMountEffects_complete (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:24683:9)
    at commitLayoutEffects_begin (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:24669:7)
    at commitLayoutEffects_begin (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:24651:11)
    at commitLayoutEffects (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:24607:3)


The above error occurred in the <PopupComponent> component:
    at PopupWithoutContext (webpack-internal:///./node_modules/@progress/kendo-react-popup/dist/es/PopupWithoutContext.js:97:28)
    at eval (webpack-internal:///./node_modules/@progress/kendo-react-popup/dist/es/Popup.js:38:67)
    at div
    at AsyncFocusBlur (webpack-internal:///./node_modules/@progress/kendo-react-common/dist/es/hocs/AsyncFocusBlur.js:30:23)
    at TimePickerWithoutContext (webpack-internal:///./node_modules/@progress/kendo-react-dateinputs/dist/es/timepicker/TimePicker.js:87:28)
    at eval (webpack-internal:///./node_modules/@progress/kendo-react-common/dist/es/hocs/withPropsContext.js:28:95)
    at component
    at Field (webpack-internal:///./node_modules/@progress/kendo-react-form/dist/es/Field.js:37:22)
  ...