Check for duplicates

• I have searched for similar issues before opening a new one.

Description

When using the arrow keys to navigate blocks with the new keyboard experimentation plugin, the keyboard nav line cursor does not scroll the new node into view if it is a field (or not a block). This is only noticeable when using the left arrow to move out as the setCurNode method appears to run multiple times, and the first time it scrolls the currently selected block into view. This has led to two modes of failure.

1. When the left arrow navigates to a field off-screen it is not scrolled into view. See video below:

2. When workspace focus is lost a while a field is the selected node, the workspace is incorrectly scrolled when focus is returned. See video below where the focus change is caused by opening and closing the toolbox:

Reproduction steps

Reproduction steps can be observed in the videos above with keypresses recorded and shown on screen. It's more about moving blocks into the necessary positions in order to observe the effects of not scrolling fields into view.

Both videos use the Blockly keyboard experimentation test page.

Stack trace

Screenshots

See videos in description.

Browsers

Chrome desktop