Tree Grid keyboard navigation does not activate cells outside the virtualized viewport

[viktorkombov]

Description

When keyboard navigation in the Tree Grid targets a cell outside the currently rendered virtualized viewport, the target cell may not be activated/selected correctly after the grid scrolls.

This can happen with navigation actions such as Arrow Up / Arrow Down, Ctrl + Home / Ctrl + End, or Tab / Shift + Tab when the target row or column is not currently rendered because of virtualization.

In this case, the Tree Grid may scroll, but the active/selected cell remains on the previous cell or moves to an incorrect cell.

The issue is easier to expose in zoneless change detection tests, but the underlying behavior appears to be related to virtualized scroll/navigation timing and is not limited to zoneless applications.

Framework

Angular

Angular Version

22.0

Ignite UI for Angular Version

22.0.x

Component / Area

Tree Grid

Browser

Chrome

Operating System

Windows 11

Command Not Working

Steps to Reproduce

1. Create a Tree Grid with fixed height and enough rows/columns to enable virtualization.
2. Focus or select a cell near the currently visible viewport.
3. Use keyboard navigation to move to a cell outside the current viewport, for example:
   • ArrowDown / ArrowUp when the target row requires vertical scrolling
   • Ctrl + End or Ctrl + Home
   • Tab or Shift + Tab when the next editable cell is outside the visible area
4. Observe the active/selected cell after scrolling completes.

Actual Result

The Tree Grid scrolls, but the target cell outside the original viewport is not activated/selected correctly.

The active/selected state may remain on the previous cell or move to an incorrect cell.

Expected Result

Keyboard navigation should scroll the Tree Grid as needed and then activate/select the intended target cell once it is rendered, including when the target cell is outside the current virtualized viewport.

Reproduction URL

Attachments