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 am using the unity plugin for a UWP unity application. On touch screen devices that don't have a keyboard or when the physical keyboard is detached, the on-screen or touch keyboard does not open automatically when an input field is selected in any loaded webpage . This was tested on Surface pro 10 and Surface book.
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
0.22.6, 0.22.7-pre.1
Framework
Unity Plugin
Operating System
Windows 11
OS Version
No response
Repro steps
Run unity UWP app with webview2 plugin implementation on a touchscreen device with detached physical keyboard.
Load any webpage with an input field and touch/select the input field.
The on-screen/touch keyboard does not open.
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered:
What happened?
I am using the unity plugin for a UWP unity application. On touch screen devices that don't have a keyboard or when the physical keyboard is detached, the on-screen or touch keyboard does not open automatically when an input field is selected in any loaded webpage . This was tested on Surface pro 10 and Surface book.
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
0.22.6, 0.22.7-pre.1
Framework
Unity Plugin
Operating System
Windows 11
OS Version
No response
Repro steps
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered: