Add hideAfter prop to the Notification component.

This will allow controlling when the notification will be hidden.

The `WorkWeekView` and `DayView` components only support displaying a continuous range of days, defined by `workWeekStart` and `workWeekEnd` (or `numberOfDays`). There is no way to specify an arbitrary set of non-consecutive weekdays (e.g., Monday, Wednesday, and Saturday) and render them as side-by-side columns in a single view.

Customers who operate on non-standard schedules — such as shift workers, part-time staff, or businesses with non-traditional work weeks — cannot represent their schedule accurately in the Scheduler without resorting to CSS workarounds that break event positioning.

Introduce a `days` prop (or equivalent) on `WorkWeekView` and `DayView` that accepts an array of `Day` enum values. When provided, the view should render only the specified days as columns, in the declared order, regardless of whether they are consecutive.

<WorkWeekView days={[Day.Monday, Day.Wednesday, Day.Saturday]} />

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

Problem:

Currently, passing props directly through customSlot and customItem triggers numerous unnecessary component rerenders. To mitigate this, official support recommends passing props via React Context and wrapping customSlot/customItem in React.memo, while explicitly specifying which props should trigger a rerender upon changing. These additional workarounds introduce a poor developer experience. It is initially unclear what needs to be implemented, and it introduces a high maintenance overhead, as any future component extensions or changes require manual monitoring to prevent regressions.

Proposal:

Please optimize the internal mechanics of customSlot/customItem so that they handle updates efficiently out of the box, eliminating the need for this boilerplate code. Below is an example that implements all the current recommended workarounds to avoid unnecessary redraws:

https://stackblitz.com/edit/react-kr5cmxga-dp96seni?file=app%2FcustomSlot.tsx 

Overview:

The KendoReact PDF Viewer renders every page of a document up front. For large PDFs this causes long initial load times and high memory use.

Expose load-on-demand / virtualized page rendering in the React component, matching the existing Kendo UI for Angular PDF Viewer which has:

• loadOnDemand - render pages as the user scrolls
• loadOnDemandPageSize - pages fetched/rendered per batch
  

Reference: https://www.telerik.com/kendo-angular-ui/components/pdfviewer/load-on-demand

This is a framework-parity gap. The same underlying rendering engine already supports on-demand loading in Angular (and virtualization has been requested for Blazor: httpzor/1594054-pdf-viewer-virtualization). React usershitting large documents currently have no first-party option and must swap to a third-party viewer.

Environment: @progress/kendo-react-pdf-viewer 10.2.0, React 19, Next.js 15.

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, 
I am looking to start using the Kendo React grid control, but I need the grid to be responsive to support viewing on a phone. I noticed that your Angular grid has this functionality, but it is missing from your React grid. 
I would like to have rows turn into individual cards when viewed on a phone. The closest thing I see in the react documentation involves hiding columns, which is undesirable.  Is there a way to add this behavior to the React grid?  If not, when will that be implemented?  
Thank you, 
Alex

ExcelExport has a prop for 'creator'. When the excel file is generated, "creator"'s value is reflected in the file's metadata

For accessibility / screen reader purposes, Title (under Description) must also be populated. Please allow a "title" prop to be accepted by the ExcelExport component.

Add the ability to apply table breakpoints to the Grid for responsive behavior.

Similar to the Bootstrap tables:

https://getbootstrap.com/docs/4.4/content/tables/#breakpoint-specific

I would like to request a new Kendo React Grid column editing option so that users can navigate editable columns using the keyboard. This feature should be similar to "navigatable" option from Kendo jQuery grid example - https://demos.telerik.com/kendo-ui/grid/editing

Thanks.

Hi, 

I'm in need of the dropdown feature in spreadsheet cells. I had been using the Kendo Spreadsheet React Wrapper which had the dropdown feature but since the latest update to Kendo React Spreadsheet I have been facing issues. Please try to get this feature as soon as possible and I'm sure this will be helpful for other users, too.

Thank you.

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: