Search Issue Tracker
Fixed in 5.2.0
Votes
0
Found in
5.1.0f2
Issue ID
699504
Regression
Yes
doNotCaptureKeyboard not working in WebGL
1. What happened
WebGL project build with Unity 5.1.0f2 with HTML content which require keyboard input is no longer working. In earlier version 5.0.1 setting parameter 'doNotCaptureKeyboard : true' to Module definition enabled keyboard input to be enabled on HTML controls running on the same page.
2. How we can reproduce it using the example you attached
Case 1:
- build included KeyboardFocus project with Unity 5.0.1 (an empty scene)
- add '<input type="text" value="" />' field to the HTML page
- add 'doNotCaptureKeyboard : true' parameter to the Module definition
- run the build in browser
- try input text to input field
=> text displayed correctly
Case 2:
- build included KeyboardFocus project with Unity 5.1.0 (an empty scene)
- add '<input type="text" value="" />' field to the HTML page
- add 'doNotCaptureKeyboard : true' parameter to the Module definition
- run the build in browser
- try input text to input field
=> BUG: cannot input text to the input field!
Comments (4)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
lucian.galiotto
Jul 20, 2015 18:48
I'm standing in Unity 5.0.1, because this problem is critical. I need to use input in HTML pages. There is a lot to fix this problem?
dark_end
Jun 24, 2015 15:15
I can confirm this since I updated from 5.0.1 to 5.1.1