NVDA reports selection changes when moving by character or line in mark mode #18290

Closed
opened 2026-01-31 06:09:27 +00:00 by claunia · 5 comments
Owner

Originally created by @LeonarddeR on GitHub (Aug 24, 2022).

Windows Terminal version

1.15.2003.0

Windows build number

22621.105

Other Software

NVDA 2022.2.1

Steps to reproduce

  1. Open terminal
  2. Press Ctrl+Shift+M
  3. press left arrow

Expected Behavior

NVDA says: >

Actual Behavior

Nvda says: >, > selected, space unselected

Originally created by @LeonarddeR on GitHub (Aug 24, 2022). ### Windows Terminal version 1.15.2003.0 ### Windows build number 22621.105 ### Other Software NVDA 2022.2.1 ### Steps to reproduce 1. Open terminal 2. Press Ctrl+Shift+M 3. press left arrow ### Expected Behavior NVDA says: `>` ### Actual Behavior Nvda says: `>, > selected, space unselected`
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:09:27 +00:00
Author
Owner

@LeonarddeR commented on GitHub (Aug 24, 2022):

In Narrator the behavior is even worse, mark mode with up/down arrow is basically unusable

The underlying issue is likely as follows. When moving through a normal text editor with an UIA implementation, that impl only fires selection events when selecting with shift+arrows, with the mouse or something else that involves text selection. On the contrary, Terminal seems to fire selection events for cursor movement as well. IMO mark mode in Terminal should behave similar to conhost in that it does not fire selection events for cursor movement.

@LeonarddeR commented on GitHub (Aug 24, 2022): In Narrator the behavior is even worse, mark mode with up/down arrow is basically unusable The underlying issue is likely as follows. When moving through a normal text editor with an UIA implementation, that impl only fires selection events when selecting with shift+arrows, with the mouse or something else that involves text selection. On the contrary, Terminal seems to fire selection events for cursor movement as well. IMO mark mode in Terminal should behave similar to conhost in that it *does not* fire selection events for cursor movement.
Author
Owner

@LeonarddeR commented on GitHub (Aug 24, 2022):

CC @codeofdusk @carlos-zamora

@LeonarddeR commented on GitHub (Aug 24, 2022): CC @codeofdusk @carlos-zamora
Author
Owner

@zadjii-msft commented on GitHub (Aug 24, 2022):

Pretty sure this is /dup #13447?

@zadjii-msft commented on GitHub (Aug 24, 2022): Pretty sure this is /dup #13447?
Author
Owner

@LeonarddeR commented on GitHub (Aug 24, 2022):

Yes, it is. Sorry for the duplicate. I should change my searching heuristics probably.
I will use the area accessibility label in the future.

@LeonarddeR commented on GitHub (Aug 24, 2022): Yes, it is. Sorry for the duplicate. I should change my searching heuristics probably. I will use the area accessibility label in the future.
Author
Owner

@ghost commented on GitHub (Aug 24, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Aug 24, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18290