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

Additional list numbers read when navigating a list in Word with UIA #9613

Closed
Qchristensen opened this issue May 23, 2019 · 2 comments · Fixed by #10467
Closed

Additional list numbers read when navigating a list in Word with UIA #9613

Qchristensen opened this issue May 23, 2019 · 2 comments · Fixed by #10467

Comments

@Qchristensen
Copy link
Member

@Qchristensen Qchristensen commented May 23, 2019

Steps to reproduce:

  1. Turn NVDA's UIA in Word option on. Open Word 365 to a blank document.
  2. Type: 1. The first
  3. Press enter and for list item 2 type "the second".
  4. Press UP ARROW.
  5. Press LEFT ARROW
  6. Press RIGHT ARROW four times.

Actual behavior:

A) At Step 4, NVDA reads "1. The first 2"
B) At Step 5 (left arrow), NVDA reads "T".
C) At step 6, NVDA reads "2", then "2. T", then "2. T", then "h"

Expected behavior:

A) NVDA should read "1. The first" (without reading 2)
B) This step is correct.
C) NVDA should read "linefeed", "2", "T", "h"

System configuration

NVDA installed/portable/running from source:

NVDA version:

NVDA 2019.1.1 installed
nvda_snapshot_alpha-17311,0d29265e

Windows version:

Windows 10 18362.1

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

Office 365 Version:
16.0.11601.20184

Other information about your system:

Other questions

Does the issue still occur after restarting your PC?

Yes

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

@leonardder
Copy link
Collaborator

@leonardder leonardder commented Oct 28, 2019

This has been an issue for a while now. While UIA is still not the default implementation, this is a major show stopper from using it, therefore assigning it p2, at least to investigate what the problem is.

@michaelDCurran Any ideas where to start looking?

@zstanecic
Copy link
Contributor

@zstanecic zstanecic commented Oct 28, 2019

michaelDCurran added a commit that referenced this issue Nov 6, 2019
…ing a range passed the end of the given outer range.

 Fix for #9613: The next bullet in MS Word is announced on the line above.

 # Please enter the commit message for your changes. Lines starting
michaelDCurran added a commit that referenced this issue Nov 6, 2019
…10467)

* UIAUtils.iterUIARangeByUnit: Doubly ensure that we do not start emitting a range passed the end of the given outer range.
 Fix for #9613: The next bullet in MS Word is announced on the line above.

 # Please enter the commit message for your changes. Lines starting

* Fix linting issues.

* Fix typo

Co-Authored-By: Leonard de Ruijter <leonardder@users.noreply.github.com>
@nvaccessAuto nvaccessAuto added this to the 2019.3 milestone Nov 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants