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
There should be a way to ignore / opt out of shortcuts while typing in an input / select / textarea element.
For the scenario below, let's assume we have a button with a shortcut of 'S' and a textarea on the same page.
With the current default (preventDefault = true), when the letter is pressed while the textarea has focus, the shortcut gets triggered and the letter does not get added to the value of the input element. This is a problem as we should be able to type 'S' in the input.
If we then configure preventDefault = false - we get the desired behavior of the letter being added to the input, however the shortcut is also triggered, which may be undesirable.
Suggest A Solution
To address the issue with minimal impact to existing users, adding a new boolean option called something like 'ignoreInInputs' could be used to alter behavior in the shortcut logic. By default, this can be set to false to keep same behavior as today.
Finally, the documentation should be updated to describe these scenarios and add examples to make this as easy to use as possible.
Thanks for your consideration!
The text was updated successfully, but these errors were encountered:
Describe The Problem To Be Solved
There should be a way to ignore / opt out of shortcuts while typing in an input / select / textarea element.
For the scenario below, let's assume we have a button with a shortcut of 'S' and a textarea on the same page.
With the current default (preventDefault = true), when the letter is pressed while the textarea has focus, the shortcut gets triggered and the letter does not get added to the value of the input element. This is a problem as we should be able to type 'S' in the input.
If we then configure preventDefault = false - we get the desired behavior of the letter being added to the input, however the shortcut is also triggered, which may be undesirable.
Suggest A Solution
To address the issue with minimal impact to existing users, adding a new boolean option called something like 'ignoreInInputs' could be used to alter behavior in the shortcut logic. By default, this can be set to false to keep same behavior as today.
Finally, the documentation should be updated to describe these scenarios and add examples to make this as easy to use as possible.
Thanks for your consideration!
The text was updated successfully, but these errors were encountered: