-
-
Notifications
You must be signed in to change notification settings - Fork 654
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
No action on 'Move selection to selected" button on first activation in Multi-select picklist #15780
Comments
Is this reproducible in Firefox as well? |
No |
Hi @Adriani90, did you get a chance to look into this issue? |
@Sweety1621 I cannot reproduce your issue with NVDA last alpha. You can test with the last alpha from this link: I tested in Chrome and Edge 119 last updates but without virtual machine.
|
In Firefox the focus does not sync reliably when I press nvda+space bar to enable focus mode. @jcsteh is the failing sync of system focus when using nvda+space bar somehow influenced by the web author in this case? I wonder why this works smoothly in Chromium browsers but not in Firefox. |
Are you pressing NVDA+space after moving focus to the list? For me, focus is moved reliably in this case. |
Thanks @Adriani90 , I turned-off |
This works: press the 'Tab' key to navigate to the left listbox, then press 'Alt + Down Arrow', and finally press 'Tab' again. This time, the 'Move' button will exhibit the expected behaviour and transfer the choice to the right listbox. I wanted to confirm about the change in the NVDA setting @Adriani90. Turing off 'Automatic focus mode for focus changes' shows the expected behaviour but is this setting feasible for users who rely on a screen reader, as it isn't the default setting? |
Automatic focus mode has been introduced actually only with the purpose of filling forms but the usage of automatic change to focus mode in day to day work with NVDA is controversial among users. Most of the users I know do not use the automatic focus mode setting. There are more other issues related to this setting indeed. Actually I was refering to another setting in my comment above, which is called "automatically move focus to focusable elements" which basically moves the system focus automatically when moving the virtual cursor in browse mode. That setting is disabled by default. I thought you might have enabled it by accident or so. |
@Sweety1621 - can you confirm whether this setting "automatically move focus to focusable elements" is enabled and causing this issue? are you still experiencing it? |
Hi Sean,
After disabling this option, we can press the 'Tab' key to navigate to the
left listbox, then press 'Alt + Down Arrow', and finally press 'Tab' again.
This time, the 'Move' button will exhibit the *expected behaviour *and
transfer the choice to the right listbox.
Thanks!
…On Wed, Jan 8, 2025 at 10:13 AM Sean Budd ***@***.***> wrote:
@Sweety1621 <https://github.com/Sweety1621> - can you confirm whether
this setting "automatically move focus to focusable elements" is enabled
and causing this issue? are you still experiencing it?
—
Reply to this email directly, view it on GitHub
<#15780 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANIPXYO76TXYNODOMWJHOWL2JSUGTAVCNFSM6AAAAABUZCFCU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZWG42DCMZQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Steps to reproduce:
This works as expected with JAWS or Voiceover.
Actual behavior:
When a user presses enter/space on the Move selection to selected button to move an item to the 'Selected' box, nothing happens on the first try. A user has to action the button a 2nd time to move the selected item over.
Focus is also lost after the 1st keyboard activation.
The issue doesnt happen in reverse when moving items from right to left.
Expected behavior:
After taking action on the Move button, space or enter should work the first time to move an item over. Focus should stay on the trigger element.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2023.2
Windows version:
Windows 11
Name and version of other software in use when reproducing the issue:
Chrome 119.0.6045.106
Other information about your system:
VM
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
The text was updated successfully, but these errors were encountered: