Reproduction steps:
1. Open the attached “Possible UI Bug.zip” project
2. Open the “SampleScene” (Assets > Scenes)
3. In the Hierarchy, select the “UIDocument” GameObject
4. In the Inspector, in the ‘Multi Column Example' Component find the ‘Workaround’ property
5. In the dropdown select “None” or “Broken”
6. Enter the Play mode
7. Press the 'S' key on the keyboard

Expected result: Selection is changed to the next element
Actual result: Selection is not changed on the first press of the key

Reproducible with: 2022.3.53f1, 6000.0.28f1, 6000.1.0a6
Couldn’t test with: 2021.3.45f1 (MultiColumnListView and MultiColumnTreeView are not supported)

Reproducible on: Windows 11
Not reproducible on: no other environment tested

Notes:
- The View will receive the event, and trigger any registered callbacks, but the selection does not change. Once a single input action is sent, it will respond to subsequent events normally
- Does not reproduce with ListView or TreeView
- If a NavigationMoveEvent is sent via code in the first Update() after the Focus() is called on the View, that event also triggers registered callbacks, but does not change the selected item. This will then result in two navigation events that do not change the selection: the one sent by code, and the one sent via user input
- If a NavigationMoveEvent is sent on the 2nd Update() after the Focus(), that event will demonstrate the behavior above, but the first user input event will behave normally
- Setting the ‘Workaround’ property to ‘Working’ shows the expected behavior