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

Inert property not synchronous for NVDA+Chrome #120

Open
ptrin opened this issue May 17, 2019 · 1 comment
Open

Inert property not synchronous for NVDA+Chrome #120

ptrin opened this issue May 17, 2019 · 1 comment

Comments

@ptrin
Copy link

ptrin commented May 17, 2019

I'm not sure whether this is a bug per se but I wanted to inform you because it contradicts the documentation provided in the readme:

Using the inert property, however, is synchronous.

Looking at this code example:

     // Remove inert of next section
     nextSection.inert = false;
     // Focus first input in next section
-    this.focusFirstInput(nextSection);
+    setTimeout(() => {
+      this.focusFirstInput(nextSection);
+    }, 5);

For some reason, pressing Space on the button that triggered this code worked properly in Chrome with NVDA, but triggering it with Enter did not. After adding a short timeout, both the Space and Enter keys work as expected. Both Space and Enter worked without the timeout in VoiceOver+Safari.

@robdodson
Copy link
Collaborator

hey @ptrin I'm surprised that the behavior would be different depending on if you activate the button with space or enter. Do you have a jsbin or something similar that we can use to reproduce the issue?

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

No branches or pull requests

2 participants