Conhost: UIA word navigation is slow #6605

Open
opened 2026-01-31 00:42:52 +00:00 by claunia · 0 comments
Owner

Originally created by @codeofdusk on GitHub (Feb 23, 2020).

Originally assigned to: @carlos-zamora on GitHub.

Environment

Windows build number: 1909 (18363.657).

Windows Terminal version (if applicable): Open Console (commit b8e33560f9).

Any other software? Yes, test build of NVDA and Open Console build used available here.

Steps to reproduce

  1. Run the included NVDA build (a patched version of nvaccess/nvda#10784 that uses native UIA word navigation and disables our workarounds in Windows Console).
  2. From advanced preferences (press insert+n/right-click tray icon -> preferences -> settings -> advanced), enable UI automation in Windows Console.
  3. Run the latest conhost from this repository (a build of commit b8e33560f9 is included in the zip).
  4. Attempt to navigate by word (numpad 4/6 with numlock disabled).

Expected behavior

NVDA quickly reads the previous or next word, similar to Windows Terminal.

Actual behavior

An approximately one second lag is observed for each word movement.

Originally created by @codeofdusk on GitHub (Feb 23, 2020). Originally assigned to: @carlos-zamora on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Windows build number: 1909 (18363.657). Windows Terminal version (if applicable): Open Console (commit b8e33560f90ff7c4b3294f83bbeabb1b6a74d3e1). Any other software? Yes, test build of NVDA and Open Console build used [available here](https://codeofdusk.com/UIASlowWordNavTest.zip). # Steps to reproduce 1. Run the included NVDA build (a patched version of nvaccess/nvda#10784 that uses native UIA word navigation and disables our workarounds in Windows Console). 2. From advanced preferences (press insert+n/right-click tray icon -> preferences -> settings -> advanced), enable UI automation in Windows Console. 3. Run the latest conhost from this repository (a build of commit b8e33560f90ff7c4b3294f83bbeabb1b6a74d3e1 is included in the zip). 4. Attempt to navigate by word (numpad 4/6 with numlock disabled). # Expected behavior NVDA quickly reads the previous or next word, similar to Windows Terminal. # Actual behavior An approximately one second lag is observed for each word movement.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6605