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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment