Description
When Grid is configured with navigatable={true} and row selection enabled, pressing Enter on an interactive element (for example a Button) inside a custom data cell can trigger row selection instead of the element's own action. This creates an accessibility and keyboard interaction conflict.
Plan
KendoReact
Steps To Reproduce
- Render a Grid with
navigatable={true} and selectable enabled.
- Add a custom data cell containing a KendoReact
Button with an onClick handler.
- Use keyboard navigation to focus the cell/button.
- Press Enter.
Sample page - https://stackblitz.com/edit/navigatable-nepaqhct?file=index.js
Screenshots or video
No response
Actual Behavior
Enter triggers row selection and the button action is not executed.
Expected Behavior
Enter should activate the focused interactive element in the custom cell (button onClick), while row selection should remain available for non-interactive cells.
Browser
Chrome
Browser version
latest
OS type
MacOS
OS version
No response
Last working version of the KendoReact package (if regression).
No response
Description
When Grid is configured with
navigatable={true}and row selection enabled, pressing Enter on an interactive element (for example a Button) inside a custom data cell can trigger row selection instead of the element's own action. This creates an accessibility and keyboard interaction conflict.Plan
KendoReact
Steps To Reproduce
navigatable={true}andselectableenabled.Buttonwith anonClickhandler.Sample page - https://stackblitz.com/edit/navigatable-nepaqhct?file=index.js
Screenshots or video
No response
Actual Behavior
Enter triggers row selection and the button action is not executed.
Expected Behavior
Enter should activate the focused interactive element in the custom cell (button
onClick), while row selection should remain available for non-interactive cells.Browser
Chrome
Browser version
latest
OS type
MacOS
OS version
No response
Last working version of the KendoReact package (if regression).
No response