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