Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
4.6.0f1
Issue ID
646106
Regression
No
Mouse input doesn't call touchscreen keyboard
Mouse input doesn't call touchscreen keyboard
Selecting input field with physical mouse, which is connected to touchscreen device, touchscreen keyboard doesn't appear.
Selecting input field with touch, touchscreen keyboard appears.
Physical mouse should work the same as touch input.
Reproducible with 4.6.0RC1 on Windows Store Apps. Also, should be reproducible on Android.
Repro steps:
1. open project "UIrc1Project";
2. build to Win Store Apps platform;
3. try clicking with connected mouse on input fields in the first scene called "Controls";
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
yoonitee
Dec 18, 2014 12:08
I disagree.
The touchscreen keyboard should only appear
1) if you touch the input control
2) if you have no keyboard.
yoonitee
Dec 18, 2014 12:08
I disagree.
The touchscreen keyboard should only appear
1) if you touch the input control
2) if you have no keyboard.