Add link menu - first item is always skipped - keyboard navigation

Bug Reports Closed
,
1

What’s The Bug?

When adding a new object link with “Add link” a context sub menu is opened. Once you use your arrow key to select an item the first item in the list is always skipped. Pressing down key always jumps to the second item in the list…

How To Reproduce It

  1. add a link with “/Add link”
  2. press enter → context menu opens
  3. use down key directly (without searching an object first)
  4. highlighted item jumps directly to the second entry

Image or Video

The Expected Behavior

normal behaviour without skipping an entry

Additional Context

Maybe the issue is, that the first item in the list is not highlightet on first loading the submenu? Because once you start to search for an item, it works properly.
I remember to have a similar behaviour also in some other submenus where you use the arrow key directly to navigate to an entry it always selects the second one first after pressing the down key.

Device

Macbook Pro 2019

OS

Ventura 13.5.1

Anytype Version

v0.39.0

Technical Information

OS version: darwin x64 13.5.1
App version: 0.39.0
Build number: build on 2024-03-05 15:37:42 +0000 UTC at #a7986fffadcc2031b1eb3372265db5dda05f4c6d
Library version: v0.32.1
Anytype Identity: AAsJHwSpaU3JKZt167Z486cREuMu9VrC25NS2ovteHyrMYNb
Analytics ID: A6x4KsqzMWtuvUoPttbvSvG9iEfVp52z9sDRYUYLhLXAeVeo
Device ID: 12D3KooWFr9H5jpNDUC9QNXn6z5sjRxdDiZmiX5QoA1sLDHeU9nA

2

Confirmed on Win 10.

Additional information:
Pressing Enter out from the empty search field, without using the arrow keys, uses the first item in the list.
The only tiny confusing thing is, that the first item isn’t highlighted.

But the best behavior would be, that the first press on arrow down key selects the first item in the list (the way as the OP expects).

Because, in the beginning has the search field the focus.
So logically it needs one press on arrow down to focus on the first item direct below the search field.

3

This report has been added to our issue tracker and received by the Development Team.

4

This issue has been fixed by the Development Team and will be implemented in an upcoming release.