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

Terminal programs: "speak typed words" provides incorrect results in some cases when "report dynamic content changes" is disabled #10942

Open
codeofdusk opened this issue Apr 5, 2020 · 2 comments

Comments

@codeofdusk
Copy link
Contributor

Steps to reproduce:

  1. Disable "report dynamic content changes" (NVDA+5) and enable "speak typed words" (NVDA+3).
  2. Open a Windows Console, UIA or legacy using the new typed character support.
  3. In a git repository, type git log.
  4. Press q to close the pager.
  5. Type "git" and press space.

Actual behaviour:

NVDA says "qgit".

Expected behaviour:

NVDA says "git".

System configuration

NVDA installed/portable/running from source:

Installed.

NVDA version:

Latest master.

Windows version:

Windows 10 1909.

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

Windows Console.

Other information about your system:

N/A

Other questions

Does the issue still occur after restarting your computer?

N/A

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

N/A

If addons are disabled, is your problem still occuring?

N/A

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

N/A

codeofdusk added a commit to codeofdusk/nvda that referenced this issue Apr 5, 2020
This saves us from scanning the old and new lines twice in _calculateNewText (once for diffing and once for finding nonblank indices), and fixes typed word reporting for 21H1 console.

This new approach does not resolve nvaccess#10942.
@codeofdusk
Copy link
Contributor Author

This was not resolved in the Windows Terminal PR, could this please be reopened?

@michaelDCurran michaelDCurran reopened this Apr 6, 2020
@Adriani90
Copy link
Collaborator

@codeofdusk how is this now with NVDA 2024.3 Beta? Are you still having this issue?

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

No branches or pull requests

3 participants