Text style navigation: Runtime error, NVDA cannot find desired offset in textInfo when using tables in MS Word with UIA disabled #16459
Comments
|
This ssems to work properly when UIA is enabled. |
There is no such text in the attached document. I assume you meant "Professional experience". But having said that, for some reason your issue doesn't repro on my computer. Just to clarify, when you say
I only have this option: |
seanbudd
added
app/microsoft-office
p3
|
Yes only when necessary is the value I was refering too.Did you try to navigate back and forth between the headings? E.g. until the last heading and back to the first via same style navigation for example?I definitely reproduce this on several machines.Von meinem iPhone gesendetAm 30.04.2024 um 00:36 schrieb mltony ***@***.***>:
Navigate to a heading (e.g. professional background)
There is no such text in the attached document. I assume you meant "Professional experience". But having said that, for some reason your issue doesn't repro on my computer. Just to clarify, when you say
Make sure UIA for MS Word is disabled in NVDA advanced settings
I only have this option:
Use UI Automation to access Microsoft Word document controls:
Only when necessary
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Yes, I confirm I can navigate back and forth between headings with styleNav commands. Navigate to different style also works as expected. |
|
Did you make sure UIA is set to "only necessary" for MS Word? For what I can say, for me style navigation does not really work in this example document at ll. I get this in the log: Note: if you restart NVDA while the document is focused the object model will not be available and UIA will be used although it is set to "only when necessary". Alt+tabbing away and back to the document makes sure you are using object model. cc: @CyrilleB79 or @lukaszgo1 can you test as well? |
Yes.
I tried restarting NVDA and Alt-tabbing back and forth and still cannot reproduce this. |
|
@burmancomp, @cary-rowen could you please test if you have this issue with UIA set to "only when necessary" for MS Word in NVDA advanced settings? |
|
I tested this and I could only reproduce it by trying "moves to the next different style text" in "Professional experience", The other commands "moves to the previous different style text, moves to the previous same style text, moves to the next same style text" all work as expected. NVDA alpha-31858
But I don't agree that this should be reverted. If the exact reason is found, it can be noted that this is an exception. |
|
I just tried again on my computer exactly what @cary-rowen described - and on my computer it works as expected without throwing any errors. Same thing for my other laptop. I am perplexed, not sure how to proceed here. |
|
I haven't seen this part of the code, are there any easy steps I can take to help debug it? |
|
That's the problem, there are no easy steps I can think of. If I could repro this, I would run this in a virtual machine and connect with a debugger to understand better what's going on. |
|
In my case, when the word document is a read-only document (i.e. not editable), the text style navigation is correct when following the steps above. |
|
I managed to reproduce this when I unchecked protected view. I go to "Academic experience" and try navigating to previous same style - only in this case it raises that exception. Now debugging. |
|
@mltony I attach a new document, in this document I definitely can reproduce this issue both with UIA enabled or disabled. |
|
@hwf1324 you seem to have UIA enabled, bookmark navigation is only when using UIA in MS Word. |
@Adriani90 No, I don't have UIA enabled, maybe my description is off. |
|
I tested with onkyo.docx in browse mode running from source. When in start of file: third next different style text gesture resulted error: File "browseMode.py", line 2321, in _expandStyle First next same style gesture press resulted: DEBUG - watchdog._waitUntilNormalCoreAliveTimeout (23:14:42.543) - watchdog (4184): When in end of file: both next (same/different) style gestures resulted error: File "browseMode.py", line 558, in |
Yes, this is reproducible for me, no matter the gestures you assign to same and different style navigation actions, with UIA disabled. From the test document you provided, if I navigate through the same style from the heading "Professional experience", I can reach the end of the document, heading "Further knowledge", and then NVDA says "No next same style text". But, if I cycle backwards to reach the top of the document, after saying "Projects and initiatives" it starts throwing that error message. Hope this helps. |
|
@Adriani90, |
To ensure: do you think I should open issue? |
) Closes #16459 Closes #16408 Closes #16458 Closes #16405 Summary of the issue: We have discovered multiple problemds with non-UIA textInfo implementation in MS Word. Some examples are #16527, #16459, #16458. Also TextInfo implenetation in Outlook has proven to be too slow for style navigation. Therefore disabling both. Description of user facing changes "Not supported in this document" message is spoken. Description of development approach Raising an error when Outlook or non-UIA Word is detected.
Steps to reproduce:
Actual behavior:
NVDA stops navigating, and the focus does not move. Following is written to the log:
Expected behavior:
Navigation should continue, e.g. within the tables or skipping the tables.
NVDA logs, crash dumps and other attachments:
n/a
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-31645,bf96860d (2024.2.0.31645)
Windows version:
Windows 11 23 H2
Name and version of other software in use when reproducing the issue:
MS Office Word 365 MSO (Version 2403 Build 16.0.17425.20176) 64 Bit
Other information about your system:
n/a
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.
n/a
If NVDA add-ons are disabled, is your problem still occurring?
No add-ons in use
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
yes
Summary-with-table-test-case.docx
The text was updated successfully, but these errors were encountered: