Enterprise Client Community

There seem to be some oddities around focus management in grid.
We have an <t:arraygrid> displaying some rows, one row is selected.
Focus is then going somewhere else on the view. Then using keyboard navigation (via TAB), or triggered by our application via requestFocus="#d...") the focus is set back to the grid.
Problem is now that apparently the "reference row" used to handle arrow-down or arrow-up key seems to be the first visible row.
More natural would be to use the selected row, or the reference row when the focus was in the grid before - which in our case would be the same.
Could this be changed?
Kind regards
Manfred

Hi Manfred,

after using the grid for 7 years, you now come up with this quite general issue! ;-) But, no problem with this at all...

The problem is: the keyboard selection and up/down management is based on the cell that currently holds the focus. If you tab into the grid from other components then you tab it from the left top to the bottom right - so the first line is selected...

I believe the best way in your scenario would be to decouple the selection (= navigation) in the grid from the active selection (= this is the item I want to select for processing). One possibility would be to use attribute SINGECLICKEXECUTE here - could you please check the demo workplace example "Grids and Trees > Grid with Details" and imagine the explicit selection being a single click, not a double click?

Regards, Björn