This disables the up/down arrow focus navigation in text fields in a different way.

[gspencergoog]

Description

In #42533, I disabled the up/down arrows for focus navigation in text fields, but we thought of a better way to do it, so this is that better way.

This change reverts the other change, and instead it tests the context of the node in the action to see if it's an EditableText node. If so, then it doesn't do the navigation action.

This is configurable in the intent, so that if you want to have arrow keys enabled in your text field (e.g. in a spreadsheet), then you can do something similar to the following in the build function for the section of the app where you want it enabled:

final Map<LogicalKeySet, Intent> _enabledNavigationKeys = <LogicalKeySet, Intent>{
  LogicalKeySet(LogicalKeyboardKey.arrowLeft): DirectionalFocusIntent(TraversalDirection.left, ignoreTextFields: false),
  LogicalKeySet(LogicalKeyboardKey.arrowRight): DirectionalFocusIntent(TraversalDirection.right, ignoreTextFields: false),
  LogicalKeySet(LogicalKeyboardKey.arrowDown): DirectionalFocusIntent(TraversalDirection.down, ignoreTextFields: false),
  LogicalKeySet(LogicalKeyboardKey.arrowUp): DirectionalFocusIntent(TraversalDirection.up, ignoreTextFields: false),
};

Widget build(BuildContext context) {
  return Shortcuts(
    shortcuts: _enabledNavigationKeys,
    child: ...
  );
}

Related Issues

Tests

• Kept existing tests to make sure that keys are ignored by default for text fields (no modifications needed)
• Added a test to verify that you can override the behavior.

Breaking Change

• No, this is not a breaking change.

[mdebbar]

Thanks a lot for improving this! LGTM.