Search Issue Tracker
Fixed in 4.6.1
Votes
1
Found in
4.6.0b20
Issue ID
637517
Regression
No
Input field selection is immediately deactivated after moving mouse
To reproduce:
1. Open the attached project
2. Open the ActivateInputFieldTest.unity scene
3. Press play. Don't move the cursor or click anywhere
4. Press Tab to activate the input field by code
5. Now move the mouse cursor for the first time. Notice how the input field is immediately deactivated
If the mouse has moved at any point before activating the input field, then it behaves as expected. The bug occurs only when an input field is selected/activated by code before the user moved the cursor or clicked at all.
Workaround: Move cursor after pressing play.
Comments (3)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Wenzil
Nov 18, 2014 01:06
This bug is fixed in Unity 4.6.0f1
Wenzil
Oct 21, 2014 07:07
This bug is not limited to input fields. Same problem for all Selectables.
Wenzil
Oct 21, 2014 06:55
The workaround doesn't work if something is selected from the initialization phase of a script since there is no opportunity to move the mouse beforehand.