-
-
Notifications
You must be signed in to change notification settings - Fork 631
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
Labels
app/microsoft-office
p3
https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Milestone
Comments
LeonarddeR
added
app/microsoft-office
p3
https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
labels
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? |
HI,
The same is with the UIA and comments.
Has somebody reviewed the PR related to comments?
When it comes to these nasty spurious list reporting, I can reproduce it even in word 2019 and outlook 2019.
From: Leonard de Ruijter <notifications@github.com>
Sent: Monday, October 28, 2019 8:14 AM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [nvaccess/nvda] Additional list numbers read when navigating a list in Word with UIA (#9613)
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 <https://github.com/michaelDCurran> Any ideas where to start looking?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#9613?email_source=notifications&email_token=ACVCDEZKLYFXNK6OK3PISQLQQ2GLBA5CNFSM4HO2N57KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECL5DYY#issuecomment-546820579> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVCDE5F3FVCQ3P3Y6U67DTQQ2GLBANCNFSM4HO2N57A> . <https://github.com/notifications/beacon/ACVCDE6DL4M2U5RG3Z4ETPLQQ2GLBA5CNFSM4HO2N57KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECL5DYY.gif>
|
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>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
app/microsoft-office
p3
https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Steps to reproduce:
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.
The text was updated successfully, but these errors were encountered: