Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.1.X, 2017.2.X
Votes
91
Found in
2017.1.1p3
Issue ID
952802
Regression
Yes
Navigating between input fields with Tab does not enable opportunity to insert the value
Steps to reproduce:
1) Open Unity and create a new project
2) Add an empty gameObject in the Hierarchy window
3) In the Inspector window, select X position and change the value, ex: 123
4) Press Tab on the keyboard to switch between input fields for a position value
5) Try to insert any number
Expected result: Input field is switched and opportunity to insert the value should be enabled (check attached video 'expected.mp4')
Actual result: Input field is switched, but there is no way to enter the value (check attached video 'actual.mp4')
Reproduced with:
2017.1.1p3, 2017.2.0f1, 2017.3.0b3
Not reproduced with:
5.6.3p4, 2017.1.1p2, 2017.2.0b11, 2017.3.0a7
Regression since:
2017.1.1p3 - 2017.1.x
2017.2.0f1 - 2017.2.x
2017.3.0b1 - 2017.3.x
Tested on the Windows machine
--------------------
Fixed in 2017.3, 2017.2.0p1 and 2017.1.2p3
Comments (30)
-
Seanm07
Nov 01, 2017 10:56
Apparently this was fixed in "2017.2.0p1" however no patches have been released for 2017.2 yet, enough though the other patches have?
Have they forgotten to release the 2017.2 patch? This issue is very annoying, especially when working on UI which involves a lot of tabbing between input fields and would love for the patch to be available asap.
-
ESludden
Oct 28, 2017 15:35
I get the same issue with Version 2017.2.0f3 As an artist I often need to set Transform values manually and this bug/feature is slowing down the workflow.
-
problemecium
Oct 26, 2017 21:23
Seems to be fixed in 2017.3.0b6 :)
-
bzmglfs
Oct 26, 2017 10:46
come ooooon guys, it's a rage-invoking kind of a little thing
-
OddParents
Oct 24, 2017 05:55
PLEASE fix this!! Seems like a small annoyance, but it absolutely messes up the workflow, especially when trying to quickly work with Transforms!
-
anthony707
Oct 23, 2017 15:52
+1 This is annoying.
-
BigToe
Oct 21, 2017 18:50
The fact that this is happening on multiple releases and patches is mind-boggling.
-
Tobias-Pott
Oct 20, 2017 08:50
Present in 2017.1.1p4 after switching from 5.6.x
I was a little bit confused as I first considered it a really bad change decision as it does not bring any benefit at all (or none I can think of).
Good to see that future versions still suffer from it and I can save my time trying those until seeing something specific in the change notes. -
problemecium
Oct 19, 2017 20:13
Confirmed still present in Beta release 2017.3.0b5.
-
shawnblais
Oct 17, 2017 18:40
Also happens in various 2017.1.x builds. Come on QA, do better!
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
Unity-Nikos
Oct 27, 2017
Fixed in 2017.3.0b6, 2017.2.0p1 and 2017.1.2p3