Command-uparrow & command-downarrow change interface focus incorrectly

Issue #424 new
Robert Leach created an issue

USE CASE: WHAT DO YOU WANT TO DO?

Zoom to selection and home a few times in a row

STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)

  1. Select a single tile
  2. Type command-uparrow to zoom to selection
  3. Type command-downarrow to zoom to home
  4. Repeat steps 2 & 3, 3 times

CURRENT BEHAVIOR

Depending on where your focus started...

On step 2, the main nav minus button gets focus and shows a blue highlight. On step 3, the zoom selection button gets the blue highlight/focus. The repeat of step 2 causes the home button to get the blue highlight/focus. The repeat of step 3 causes the row search field to get the blue highlight/focus. From then on, the keyboard actions no longer affect the matrix, but rather affect the text/cursor in the row search text box.

EXPECTED BEHAVIOR

Keyboard shortcuts should not move the focus from the matrix & nav buttons to the search boxes. Focus changing does make sense when the user is using the mouse and the buttons for navigation. Specifically, command-downarrow should change focus in the same way that focus changes when the home button is clicked:

upon command-down-arrow:

  • when a selection exists: focus changes to zoom selection
  • when no selection exists: focus changes to +

upon command-up-arrow:

  • when a selection exists: focus changes to home
  • when no selection exists: focus changes to -

DEVELOPERS ONLY SECTION

SUGGESTED CHANGE (Pseudocode optional)

none

FILES AFFECTED (where the changes will be implemented) - developers only

unknown

LEVEL OF EFFORT - developers only

minor

COMMENTS

Comments (10)

  1. Christopher Keil repo owner

    This happens with multiple shortcut combos. Sometimes the searchbox is randomly selected.

  2. Robert Leach reporter

    Why should multiple shortcut combos ever move the focus to the search box? I would think that the only thing that should change the focus to the search box would be command-f.

  3. Log in to comment