Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split reportstatusline script in to two, one for reading and one for moving navigator object into it #8600

lukaszgo1 opened this issue Aug 6, 2018 · 2 comments · Fixed by #12771


Copy link

lukaszgo1 commented Aug 6, 2018

Is your feature request related to a problem? Please describe.

As a user who works all the time with cared moves review cursor off and focus moves navigator set to off also, I am extremely frustrated when i want to look at the status bar of my current application only to realize a while later, that the position of my navigator object was changed without good reason.

Describe the solution you'd like

For me the best solution would be to:

  1. make reportstatusline script only report, spell and copy the information's and keep it assigned into NVDA+end
  2. create separate Movetostatusline script which will move navigator object to the status bar. This script wouldn't be assigned by default.

Describe alternatives you've considered

I;ve thought about assigning a shortcut to the movetostatusbar script but it seems to me, that most users don't even realize that the navigator object is moved due to the fact, that the options follow focus and cared are on by default.

Additional context

The proposed approach has several advantages:

  1. It is familiar to users migrating from another screen readers.
  2. The sighted users do not have to move mouse from they working position to check status bar content.
Copy link
Contributor Author

@michaelDCurran @feerrenrut Is this something which you can commend on. For me the current behavior is illogical and honestly frustrating at times.

Copy link
Contributor Author

I've updated pr description according to the new feature request template.

seanbudd pushed a commit that referenced this issue Aug 27, 2021
…e for moving review cursor into its location (#12771)

Link to issue number:
Closes #8600
Implements part of #7314

Summary of the issue:
Currently when reading status bar with NVDA+END review cursor is unconditionally moved to its location. This is inconsistent with all other commands for retrieving information and aside from that is extremely annoying for people working with review cursor now following the caret (I've been in a situation in which I've left review cursor somewhere either because I wanted to monitor a given object for changes, or because I was following some documentation with review cursor in a separate window and wanted to avoid unnecessary alt tabbing and lost my review position because I had to check something on a status bar countless times).

Description of how this pull request fixes the issue:
Review cursor is no longer moved to the location of the status bar. There is a separate script (no gesture assigned by default) which moves review cursor there. As described in #7314 I took this opportunity to split script for reading status bar into a separate ones for reading, spelling and copying.

Testing strategy:
With NVDA+end made sure that first press still reads, second spells and third copies. Made sure that after each of these operations review cursor has not been moved. Tested each of the newly introduced scripts made sure they work. Compiled user guide - ensured it renders as expected.
@nvaccessAuto nvaccessAuto added this to the 2021.3 milestone Aug 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
2 participants