Search Issue Tracker
Won't Fix
Votes
1
Found in
5.4.1f1
Issue ID
834638
Regression
No
[UWP] WebView doesn't receive most of the keyboard input
Steps to reproduce:
1. Create new project and build as Universal 10 target
2. Open built solution and at the end of MainPage.xml.cs constructor add:
var simpleWebView = new WebView();
simpleWebView.Source = new Uri("https://google.com");
var someDialog = new ContentDialog();
someDialog.Content = simpleWebView;
someDialog.ShowAsync();
3. In Package.appxmanifest enable Internet Capability
4. Run solution
5. In search bar type anything. Notice that you can type until splash screen shows up
Not reproducible: 5.3.3p2
Reproduced with: 5.3.6p6, 5.4.1p2, 5.5.0b5
Why won't fix: Unity cannot properly detect when different XAML elements get focused because not all of them tell us they're focused, so we cannot reliably stop processing input. A workaround in this case is to call UnitySetInput(false) when you show WebView and call UnitySetInput(true) when you want Unity to start processing input again.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment