let keyboard focus consistently follow switch pane keyboard shortcuts

[maxheld83]

Observed behavior:

1. I have, say, the console in focus.
2. I hit the keyboard shortcut to "show build pane"
3. I use the arrow key to navigate (a typically pretty long) build pane.
   None of then nav keys work to navigate the build log. The keyboard focus actually stays inside the console..

Now for the inconsistencies:

• If, in addition, I click into the build log, I can navigate it with the nav keys as expected.
• If I navigate from the console to the help or packages pane via keyboard shortcut "show help pane" I have focus and can use the nav keys.
• I can never get cursor focus (for nav keys) for the files pane, no matter how I switch into it.

I think it would be super cool if I could use nav keys inside other (long) panes, too, irrespective of how I switched to them.
Build logs, in particular, need to be perused quite frequently, and they tend to be quite long.
My assumption as a user was actually that whenever I "show pane" something, it should also have focus.

Not quite sure whether this is a bug report or feature request; could be either, depending on what the intended capabilities of RStudio are.

RStudio Edition : Desktop
RStudio Version : 1.2.5013
OS Version : macOS 10.14.6
R Version : 3.6.1

[gtritchie]

Thanks for the report! We are working on these sorts of issues in the RStudio 1.3 release as part of overall accessibility improvements.

[gtritchie]

Moving out of 1.3; I am fixing these pane-by-pane (probably not all the panes for 1.3); in 1.4 hope to make a more general set of focus handling fixes.

[hrbrmstr]

Not sure if this is somewhere else, but if I'm in a package project and am in a source pane and then key-shortcut build the pkg, it'd be super less frustrating to have the focus stay in the source pane.

[gtritchie]

Not sure if this is somewhere else, but if I'm in a package project and am in a source pane and then key-shortcut build the pkg, it'd be super less frustrating to have the focus stay in the source pane.

Worth having its own issue, there will be cases like this I want to be aware of as I make overall keyboard focus improvements. Thanks!

[gtritchie]

I consider this a stretch goal for 1.4. It is very critical for keyboard and/or screen-reader users, but fixing this across the board is probably not going to happen given the code complexity. Most likely will end up breaking this into some much more targeted fixes for specific scenarios in 1.4 (like, 3 or 4 panes at most).

[hrbrmstr]

Aye. I'm nearly done with a massive project that involved alot of UX interaction (vs coding through an Rmd or spin script) and it was super painful, still, but b/c of the large amount of interaction I could see where this behavior would be spread across multiple bits of the codebase and trying to nail it perfectly would be a ton of work. On the plus side, I'm getting much better at automatically hitting ctrl-1 after certain ops :-)

…

On Jul 6, 2020, at 13:51, Gary ***@***.***> wrote: I consider this a stretch goal for 1.4. It is very critical for keyboard and/or screen-reader users, but fixing this across the board is probably not going to happen given the code complexity. Most likely will end up breaking this into some much more targeted fixes for specific scenarios in 1.4 (like, 3 or 4 panes at most). — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[gtritchie]

... On the plus side, I'm getting much better at automatically hitting ctrl-1 after certain ops :-)

Yah. It is painful for a keyboard only user for sure. Will make some selective improvements, hopefully, or discover a previously unknown cache of caffeine and/or time travel and get the whole thing fixed.

[hrbrmstr]

Whatever I can do to help test/triage just lemme know.

[gtritchie]

Moving out of 1.4 (sigh), may selectively pull in some more specific fixes to 1.4 if time permits.

[hrbrmstr]

No worries. The command palette and rainbow parens more than make up for it :-)

…

On Jul 8, 2020, at 17:24, Gary ***@***.***> wrote: Moving out of 1.4 (sigh), may selectively pull in some more specific fixes to 1.4 if time permits. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, per https://github.com/rstudio/rstudio/wiki/Issue-Grooming. Thank you for your contributions.

[gtritchie]

Important for keyboard-only users.