-
-
Notifications
You must be signed in to change notification settings - Fork 842
Focus mode gets stuck when native selection is enabled #19075
Copy link
Copy link
Labels
app/chromeapp/firefoxbugfeature/focus-modep3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Description
Activity
Metadata
Metadata
Assignees
Labels
app/chromeapp/firefoxbugfeature/focus-modep3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Brief summary
When forcing focus mode with
nvda+spacein Chrome or Firefox, with Native selection enabled, focus gets stuck on the current lineSteps to reproduce
For example, try the steps from the system
test_i7562:open data:text/html,<div contenteditable="true"><p>before</p><ul><li>frogs</li><li>birds</li></ul><p>after</p></div>nvda+spacedownArrowfrom "before"Note NVDA will not leave "before"
Actual behavior
NVDA gets stuck on the line in focus mode
Expected behavior
You can navigate from the line with downArrow
NVDA logs, crash dumps and other attachments
No response
NVDA type
installed copy, portable copy, source copy, installer/launcher copy
NVDA version
2025.3, 2026.1 alphas
Have you tried any other versions of NVDA? If so, please report their behaviors.
No response
Windows version
Win 11
Name and version of other software in use when reproducing the issue
Chrome 141
Firefox 143
Other information about your system
No response
Does the issue still occur after restarting your computer?
I have restarted my computer and the issue still occurs
If NVDA add-ons are disabled, is your problem still occurring?
I have restarted NVDA with add-ons disabled and the issue still occurs
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
I have run the COM Registration Fixing Tool and the issue still occurs