Skip to content

Excel. Braille cursor doesn't move to symbol when routing button is pressed #18153

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

Open
sevapopov2 opened this issue May 24, 2025 · 0 comments
Open
Labels
app/microsoft-office needs-technical-investigation A technical investigation is required to progress the issue. p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@sevapopov2
Copy link

Preconditions:

  • Braille display is connected
  • UI Automation is disabled for Excel
  • There is a cell with the data for example text

Steps to reproduce:

  1. Navigate to a cell with a text in Excel.
  2. Press f2 to edit the cell.
  3. Press the routing button on a braille display on the needed symbol.

Actual behavior:

Braille cursor doesn't move to the symbol navigated with routing button. It stays in the end of a line or a symbol that was navigated with keyboard arrows.

Expected behavior:

Braille cursor moves to the symbol navigated with routing button.

NVDA logs, crash dumps and other attachments:

Routing issue in excel with braille display.log

System configuration

NVDA installed/portable/running from source:

Installed.

NVDA version:

2024.4.2 (2024.4.2.35031).

Windows version:

Windows 11 Pro, 24H2 (26100.4061).

Name and version of other software in use when reproducing the issue:

Microsoft® Excel® for Microsoft 365 MSO (version 2504 built 16.0.18730.20186) 64-bit

Other information about your system:

Braille display:
Hims QBrailleXL.

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.

No.

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 p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. needs-technical-investigation A technical investigation is required to progress the issue. app/microsoft-office labels May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app/microsoft-office needs-technical-investigation A technical investigation is required to progress the issue. p3 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