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
Pressing the tab key seems to trigger the default behavior. The switch that is preventing defaults for Entered could be extended to account for this change.
This change should fix it:
handleOnKeydown = (e: React.KeyboardEvent<HTMLInputElement>) => {
switch (e.which) {
case 13:
e.preventDefault();
break;
case 9:
e.preventDefault();
break;
case 8:
if (!e.currentTarget.value) {
this.removeEmail(this.state.emails.length - 1);
}
break;
default:
}
};
handleOnKeyup = (e: React.KeyboardEvent<HTMLInputElement>) => {
switch (e.which) {
case 13:
this.findEmailAddress(e.currentTarget.value, true);
break;
case 9:
this.findEmailAddress(e.currentTarget.value, true);
break;
default:
}
};
The text was updated successfully, but these errors were encountered:
Just for other folks who come along - this change makes 0.5.2 incompatible with basic keyboard navigation - a core accessibility concern. Keyboard nav users would expect to hit tab in a regular input to advance to the next field. In this case, focus is trapped in the element.
Our team is pinning to 0.5.1 - perhaps we will be able to submit a PR.
Pressing the tab key seems to trigger the default behavior. The switch that is preventing defaults for Entered could be extended to account for this change.
This change should fix it:
The text was updated successfully, but these errors were encountered: