-
Notifications
You must be signed in to change notification settings - Fork 9.3k
UIA in conhost: issues with visible ranges #5481
Copy link
Copy link
Closed
Labels
Area-AccessibilityIssues related to accessibilityIssues related to accessibilityIssue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirementsProduct-ConhostFor issues in the Console codebaseFor issues in the Console codebase
Milestone
Metadata
Metadata
Assignees
Labels
Area-AccessibilityIssues related to accessibilityIssues related to accessibilityIssue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirementsProduct-ConhostFor issues in the Console codebaseFor issues in the Console codebase
Type
Fields
Give feedbackNo fields configured for issues without a type.
Environment
Steps to reproduce
Download this list of domains.
Start Windows Console and NVDA (with UIA in Windows Console enabled in advanced preferences).
Run a python interpreter:
python.Run:
fin=open("domains.txt")
fin.readlines()
Expected behaviour
Like in pre-21H1 conhost and Windows Terminal 0.11, NVDA reads current output immediately.
Actual behaviour
At this point, NVDA's auto-read lags far behind the actual output in the buffer. Quitting Python with
quit()continues reading very old output.Context
When a text change event is received, NVDA takes a diff of the old and new text and reads only the changed portion of the text. Maybe there's a bug in our diffing algorithm (implemented here, in
LiveText._calculateNewText)?