-
-
Notifications
You must be signed in to change notification settings - Fork 768
Magnifier - Text caret is not followed in NVDA Python console #19746
Copy link
Copy link
Labels
audience/low-visionPR or issue is relevant to sighted or low vision usersPR or issue is relevant to sighted or low vision usersfeature/magnifierp3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
audience/low-visionPR or issue is relevant to sighted or low vision usersPR or issue is relevant to sighted or low vision usersfeature/magnifierp3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Steps to reproduce
NVDA+control+Zto open NVDA Python consolea = "Hello world"leftArrowto move the caret after the "d"Actual behavior
Expected behavior
The zoomed view should follow the caret while typing, no matter if the caret is at the end of the line.
NVDA logs, crash dumps and other attachments
N/A
System configuration
NVDA installed/portable/running from source
Running from source
NVDA version
Last master (commit d8bf309)
Windows version
Windows 11 23H2 (AMD64) build 22631.6649
Name and version of other software in use when reproducing the issue
N/A
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
Not tested. Magnifier is quite new (only in alpha branch for now).
If NVDA add-ons are disabled, is your problem still occurring?
Yes, even tested with a brand new config folder.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested, unrelated.