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

MS Word: selection is not reported correctly when using arrows while in "extend selection" mode #17450

Open
CyrilleB79 opened this issue Nov 28, 2024 · 0 comments
Labels
app/microsoft-office p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@CyrilleB79
Copy link
Collaborator

CyrilleB79 commented Nov 28, 2024

Rewriting more clearly from #3293 what remains to do.

In "extend selection" mode, Word allows to select text using normal navigation commands (arrows, pgUp/Down, home, end, control+arrows, etc.) instead of using these keys combined with shift. When doing so, the selection update is not reported correctly.

Below is an example described in details:

Steps to reproduce:

  1. In a blank Word document, write "Hello world!"
  2. Put your caret between "l" and "o"
  3. Press f8 to enable "extend selection" mode
  4. Press f8 again to select "Hello "
  5. Press leftArrow
  6. Press rightArrow
  7. Press escape

Actual behavior:

The following happens:
5. "w" is selected, but "H" is reported
6. "w" is unselected, but "H" is reported

Also, optionally:
3. Nothing is reported
7. Nothing is reported

Expected behavior:

The following should happen:
5. "w selected" should be reported as if shift+leftArrow was pressed
6. "w unselected" should be reported as if shift+rightArrow was pressed

Also, optionally:
3. "Selection mode enabled" should be reported
6. "Selection mode disabled" should be reported

But these two last points are much less critical.

NVDA logs, crash dumps and other attachments:

N/A

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

2024.4.1

Windows version:

10

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 re-tested, but was already present in previous versions.

If NVDA add-ons are disabled, is your problem still occurring?

Yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes

@seanbudd seanbudd added p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. labels Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app/microsoft-office p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

No branches or pull requests

2 participants