SpatialNavigationVirtualizedList AutoScroll

[Veryyapeee]

Describe the bug
While using autoscroll on list, when user is focused, it's causing some weird behaviour in terms of DPAD.

To Reproduce

setInterval(() => {
ref.current.focus(prevActiveIndex + 1)
},10 * 1000)

<SpatialNavigationVirtualizedList ref={ref} renderItem={() => <SpatialNavigationFocusableView/>} />

When autoscroll happens, and I'm still focused on the list, and then press the left/right arrow, the focus behaves, like it's on the last element that I've focused using DPAD, not the imperative focus() method.

To visualize that:
I've focused list on index 1.
Not pressing anything -> autoscroll focused element with index 3.
Pressing right -> instead of element with index 4 being focused, element with index equal to 2 is focused

Expected behavior
DPAD is following/tracking the focus() method call

Version and OS

• Library version: [3.5.0]
• React Native version: [0.73.6]
• OS [web]

Additional context
Add any other context about the problem here.

[Veryyapeee]

I've managed to work around it by using something like

const elementsRefs = useRef<SpatialNavigationNodeRef[]>([]);

const setRef = useCallback(
  (index: number) => (element: SpatialNavigationNodeRef) => {
    elementsRefs.current[index] = element;
  },
  [],
);

I'm assigning ref to each element in dataset. And each time when I'm setting focus on the list, I'm also focusing the element imperatively.

Seems like it's working, but, it would be cool if I won't have to do stuff like that.

Is it a bug, or maybe I'm missing something?

[pierpo]

Hey! It looks like a bug. It's nice that you have a workaround. Indeed, we'd expect something simpler!
Thank you for reporting it 😊

[pierpo]

Hey! I'm not sure I really solved the issue, but I did solve some race conditions with 4.0.1 regarding lists + imperative focus. Can you try again in 4.0.1, without your workaround? 😁