Check for duplicates
Problem
#8803 removes the explicit creation of a TabNavigateCursor, because tab is now used to move within the page instead of within Blockly.
However, it's fairly standard on the web for tab to navigate to the next editable field when you are already editing.
Request
@kmcnaughtsuggested "How about a middle ground of navigating to the next editable field within the same block and opening the editor, falling back to doing nothing if there are no more editable fields in that block? I can see that being able to tab to the next field is a nicer flow than having to Esc and arrow multiple times."
Reimplement tabbing between editable input fields, per the suggestion above. Put this code in the LineCursor instead of creating a new cursor just-in-time. Wire up to the appropriate tab listener.
Alternatives considered
Remove tabbing between fields entirely.
Additional context
No response
Check for duplicates
Problem
#8803 removes the explicit creation of a
TabNavigateCursor, because tab is now used to move within the page instead of within Blockly.However, it's fairly standard on the web for tab to navigate to the next editable field when you are already editing.
Request
@kmcnaughtsuggested "How about a middle ground of navigating to the next editable field within the same block and opening the editor, falling back to doing nothing if there are no more editable fields in that block? I can see that being able to tab to the next field is a nicer flow than having to Esc and arrow multiple times."
Reimplement tabbing between editable input fields, per the suggestion above. Put this code in the
LineCursorinstead of creating a new cursor just-in-time. Wire up to the appropriate tab listener.Alternatives considered
Remove tabbing between fields entirely.
Additional context
No response