When reviewing the "Keyboard Support" demo for the treelist I noticed that the selection made using the keyboard doesn't follow later selections made by the mouse.
To test this:
To test this:
- Navigate to the demo and select a row (item) with your MOUSE.
- Arrow up or down to a different row with the KEYBOARD.
- With this new selection made, use your MOUSE to select a different row.
- Navigate up or down using your KEYBOARD.
What I would expect is that final keyboard nav would start from my latest mouse click however my mouse click is ignored and, Instead, the keyboard nav picks up from the last row navigated to via the keyboard (where it left off).
It would appear that the selection made by the mouse and keyboard are independent of one another? How should I keep these two methods of selection in sync so that the keyboard follows the latest selection (regardless of what created the selection)?