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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment