You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Make sure you didn't type anything in the NVDA+f edit field.
Go to a document that you need text found for
Go to the end of the document
Press NVDA+shift+f3
Type the word
NVDA will say text not found. But when you press NVDA+shift+f3 again NVDA will be able to find the word you're looking for.
Actual behavior:
When steps 4 and 5 are complete NVDA doesn't try to find previous result, it tries to go to the next result which fails because the currsor is at the end of the document.
Expected behavior:
When steps 4 and 5 are applied NVDA should be able to find last occurrance
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2020.3
Windows version:
2004
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.
2020.2, issue was there
If addons are disabled, is your problem still occuring?
Did you try to run the COM registry fixing tool in NVDA menu / tools?
The text was updated successfully, but these errors were encountered:
Steps to reproduce:
Actual behavior:
When steps 4 and 5 are complete NVDA doesn't try to find previous result, it tries to go to the next result which fails because the currsor is at the end of the document.
Expected behavior:
When steps 4 and 5 are applied NVDA should be able to find last occurrance
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2020.3
Windows version:
2004
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.
2020.2, issue was there
If addons are disabled, is your problem still occuring?
Did you try to run the COM registry fixing tool in NVDA menu / tools?
The text was updated successfully, but these errors were encountered: