You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a hierarchical (parent–child) grid structure, keyboard navigation using the Up and Down arrow keys correctly moves focus between parent and child cells.
For example, focus can move from a parent row (e.g. Parent 0) to its child row (e.g. Child 0-0), or from a parent row to a child row in another hierarchy level.
However, when the focus moves from a parent row to a child row via keyboard navigation, the child grid’s onActiveNodeChange event is not triggered, even though the focus has clearly moved to the child cell.
This behavior makes it difficult to reliably detect parent-to-child navigation when users navigate using the keyboard.
Steps to reproduce
Create a hierarchical grid with parent and child rows.
Set up an event handler for the child grid’s onActiveNodeChange event.
Focus a parent row.
Use the Up or Down arrow keys to navigate to a child row.
Result
The focus moves to the child row as expected, but the child grid’s onActiveNodeChange event is not fired.
Expected result
When focus moves from a parent row to a child row via keyboard navigation, the child grid’s onActiveNodeChange event should be triggered so that the navigation can be detected consistently.
Description
When using a hierarchical (parent–child) grid structure, keyboard navigation using the Up and Down arrow keys correctly moves focus between parent and child cells.
For example, focus can move from a parent row (e.g. Parent 0) to its child row (e.g. Child 0-0), or from a parent row to a child row in another hierarchy level.
However, when the focus moves from a parent row to a child row via keyboard navigation, the child grid’s onActiveNodeChange event is not triggered, even though the focus has clearly moved to the child cell.
This behavior makes it difficult to reliably detect parent-to-child navigation when users navigate using the keyboard.
Steps to reproduce
Result
The focus moves to the child row as expected, but the child grid’s onActiveNodeChange event is not fired.
Expected result
When focus moves from a parent row to a child row via keyboard navigation, the child grid’s onActiveNodeChange event should be triggered so that the navigation can be detected consistently.
Attachments
c-00245333-app2.zip
msedge_b8KYkTWZRG.mp4