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
In our chat application, we often move focus back to the message field after an action such as deleting a message has been performed. Unfortunately, this opens up the virtual keyboard in many cases, so we disable this behavior if we think we're on a mobile device. We currently check this using screen size, but that's not a great heuristic.
It would be great if there were a way to check if moving focus to an input or contentEditable element would cause an on-screen keyboard to open. We might be able to solve this with the inputPanelPolicy proposed in #225, but that would mean blocking the keyboard by default, and then re-enabling it in the cases when we want it to appear, and I'd prefer to do it the other way around.
The text was updated successfully, but these errors were encountered:
@bigblind You could also set the virtualKeyboardPolicy to manual on focus and then switch the value to auto after focus is inside the editable element. That way the VK won't show up automatically on focus, but it will if the user taps on the editable element. The virtualKeyboardPolicy attribute is described here.
In our chat application, we often move focus back to the message field after an action such as deleting a message has been performed. Unfortunately, this opens up the virtual keyboard in many cases, so we disable this behavior if we think we're on a mobile device. We currently check this using screen size, but that's not a great heuristic.
It would be great if there were a way to check if moving focus to an input or contentEditable element would cause an on-screen keyboard to open. We might be able to solve this with the inputPanelPolicy proposed in #225, but that would mean blocking the keyboard by default, and then re-enabling it in the cases when we want it to appear, and I'd prefer to do it the other way around.
The text was updated successfully, but these errors were encountered: