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 have added a modal with a form in it and it seems that if autoinit is run multiple times for whatever reason, the keyboard listener is bound multiple times, so every time you press the tab key to go to the next field, you end up somewhere not expected.
If I set [--tab-accessibility-limited:false], and don't use the focus trap, the tab key works as expected.
Looking through the autoinit code, it seems like a if a check was added to ensure that the keyboard listener is only bound once, it should fix the issue.
The text was updated successfully, but these errors were encountered:
I have added a modal with a form in it and it seems that if autoinit is run multiple times for whatever reason, the keyboard listener is bound multiple times, so every time you press the tab key to go to the next field, you end up somewhere not expected. If I set [--tab-accessibility-limited:false], and don't use the focus trap, the tab key works as expected.
Looking through the autoinit code, it seems like a if a check was added to ensure that the keyboard listener is only bound once, it should fix the issue.
Thanks for your comment. We will check this and improve it in the next version.
I have added a modal with a form in it and it seems that if autoinit is run multiple times for whatever reason, the keyboard listener is bound multiple times, so every time you press the tab key to go to the next field, you end up somewhere not expected.
If I set [--tab-accessibility-limited:false], and don't use the focus trap, the tab key works as expected.
Looking through the autoinit code, it seems like a if a check was added to ensure that the keyboard listener is only bound once, it should fix the issue.
The text was updated successfully, but these errors were encountered: