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

Say all is interrupted when using find next/previous commands #11563

Closed
CyrilleB79 opened this issue Sep 4, 2020 · 1 comment · Fixed by #11564
Closed

Say all is interrupted when using find next/previous commands #11563

CyrilleB79 opened this issue Sep 4, 2020 · 1 comment · Fixed by #11564
Milestone

Comments

@CyrilleB79
Copy link
Collaborator

CyrilleB79 commented Sep 4, 2020

Steps to reproduce:

  • In keyboard options, enable "Allow skim reading" option
  • Go to any webpage, e.g.: https://www.nvaccess.org/
  • Press NVDA+control+F to search a term, e.g. "NVDA".
    *Press NVDA+DownArrow to start SayAll
  • Press NVDA+F3

Actual behavior:

NVDA:

  • sets the virtual cursor on the next occurrence of the searched word
  • reads a little bit of text (from the searched word to the end of the line)
  • stops reading

Expected behavior:

NVDA:

  • sets the virtual cursor on the next occurrence of the searched word
  • continues reading in say all from the new position of the virtual cursor onward, i.e. from the next occurrence of the searched word onward.

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

2020.2

Windows version:

Win 10

Name and version of other software in use when reproducing the issue:

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

Not now but I remember it has always behaved this way.

If addons are disabled, is your problem still occuring?

Yes

Did you try to run the COM registry fixing tool in NVDA menu / tools?

No

@CyrilleB79
Copy link
Collaborator Author

I have just updated the actual result and expected result in the initial description of this issue, as asked in #11564 (comment)

This should be clearer now (I hope so!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants