Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
LeonarddeR opened this issue Aug 24, 2022 · 5 comments
Closed
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@LeonarddeR
Copy link

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

@LeonarddeR LeonarddeR added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Aug 24, 2022
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Aug 24, 2022
@LeonarddeR
Copy link
Author

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
Copy link
Author

CC @codeofdusk @carlos-zamora

@zadjii-msft
Copy link
Member

zadjii-msft commented Aug 24, 2022

Pretty sure this is /dup #13447?

@LeonarddeR
Copy link
Author

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

@ghost
Copy link

ghost commented 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 ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants