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

No action on 'Move selection to selected" button on first activation in Multi-select picklist #15780

Closed
Sweety1621 opened this issue Nov 13, 2023 · 11 comments · Fixed by #17598
Closed
Labels
app/chrome needs-technical-investigation A technical investigation is required to progress the issue. p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Milestone

Comments

@Sweety1621
Copy link

Sweety1621 commented Nov 13, 2023

Steps to reproduce:

  1. Go to https://developer.salesforce.com/docs/component-library/bundle/lightning-dual-listbox/example
  2. Turn on NVDA
  3. Focus on Available list
  4. Select a value and then press space/enter on the 'Move selection to selected' field
  5. Notice it doesn't work the 1st time and focus is lost
  6. Activate it a 2nd time

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

@Adriani90
Copy link
Collaborator

Is this reproducible in Firefox as well?

@Sweety1621
Copy link
Author

Is this reproducible in Firefox as well?

No

@seanbudd seanbudd added app/chrome needs-technical-investigation A technical investigation is required to progress the issue. p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. labels Nov 21, 2023
@Sweety1621
Copy link
Author

Hi @Adriani90, did you get a chance to look into this issue?

@Adriani90
Copy link
Collaborator

@Sweety1621 I cannot reproduce your issue with NVDA last alpha. You can test with the last alpha from this link:
https://www.nvaccess.org/files/nvda/snapshots/

I tested in Chrome and Edge 119 last updates but without virtual machine.

  1. When I navigate in browse mode with arrow keys to the available list, I press enter on the country, NVDA reports "selected". Then I press down arrow, NVDA says "move item to selected", I press enter and the item is moved as expected. This works both in Chrome and Firefox without loosing focus. Is automatic focus focusable elements turned off in your NVDA browse mode settings? If not, please turn it off and try to reproduce again.

  2. When i navigate in focus mode to the list, in Chrome and Edge I press up and down arrow to select a country, then i press tab and then enter to move the item to the selected list. It works as expected.

@Adriani90
Copy link
Collaborator

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.

@jcsteh
Copy link
Contributor

jcsteh commented Nov 30, 2023

Are you pressing NVDA+space after moving focus to the list? For me, focus is moved reliably in this case.

@Sweety1621
Copy link
Author

Sweety1621 commented Dec 6, 2023

Thanks @Adriani90 , I turned-off Automatic focus mode for focus changes and it's showing the expected behaviour in Chrome. However, it only works once when I change the settings, pressing NVDA+space doesn't work later.

@Sweety1621
Copy link
Author

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?

@Adriani90
Copy link
Collaborator

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.
I will let this open as well since it seems to be reproducible when this setting is enabled.

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.

@seanbudd
Copy link
Member

seanbudd commented Jan 8, 2025

@Sweety1621 - can you confirm whether this setting "automatically move focus to focusable elements" is enabled and causing this issue? are you still experiencing it?

@Sweety1621
Copy link
Author

Sweety1621 commented Jan 8, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app/chrome needs-technical-investigation A technical investigation is required to progress the issue. 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

Successfully merging a pull request may close this issue.

4 participants