You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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:
Looking at this code example:
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.
The text was updated successfully, but these errors were encountered: