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

Mouse event fired incorrectly when NVDA is paired with firefox #7646

Closed
stevenbriscoeca opened this issue Oct 4, 2017 · 8 comments
Closed

Comments

@stevenbriscoeca
Copy link

stevenbriscoeca commented Oct 4, 2017

This bug has been found in this repo ten1seven/what-input#68 (comment). It might be NVDA causing it.

Steps to reproduce:

Notes : Use NVDA and firefox.

@ten1seven created this codepen to test: https://codepen.io/ten1seven/pen/yzPYrb?editors=1010

  • Open the console
  • Navigate by keyboard to the checkbox with your keyboard
  • Use the spacebar to toggle the value of the checkbox

Expected behavior:

In other browsers, you should see the keyup/keydown events firing, but with NVDA+Firefox only mouse events fire, even down to the checkbox itself. (comment taken from ten1seven/what-input#68 (comment))

System configuration:

NVDA version:

2017.2

Windows version:

Microsoft Windows 7 [version 6.1.7601]

@Adriani90
Copy link
Collaborator

@StephenBe is this issue still reproducible in NVDA with last Alpha?
cc: @jcsteh

@stevenbriscoeca
Copy link
Author

Hi @Adriani90 yes I just tried it in alpha-16281,2b96213a and it the same result

@Adriani90
Copy link
Collaborator

cc: @feerrenrut

@jcsteh
Copy link
Contributor

jcsteh commented Mar 31, 2020

Probably the same as #4903. In browse mode, space/enter is overridden to activate (which is a click for a checkbox).

@Adriani90
Copy link
Collaborator

@jcsteh does it mean that in focus mode this should work as expected?

@jcsteh
Copy link
Contributor

jcsteh commented Dec 14, 2020

Yes.

@Adriani90
Copy link
Collaborator

I don't see a difference here between Firefox and other browsers like Chrome or Edge.

@jcsteh given that such custom key events are mostly meant to work in focus mode rather than browse mode, is it ok to close this? Or is there a use case for this to work in browse mode as well?

@Adriani90
Copy link
Collaborator

I am closing as per comments above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants