Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.7.0
1.8.0-pre.1
1.8.0-pre.2
Issue ID
ISXB-754
Regression
No
Caret is lower than the center of the textbox when adding a Device Type to a Control Scheme in the Input Actions Editor
How to reproduce:
1. Open the “LowCaret.zip“ project
2. Open "New Controls.inputactions" in the Assets folder
3. Click "No Control Schemes" dropdown In the Input Actions Editor window
4. Click the "Add Control Scheme..." button
5. Click the “+” sign to add Device Type to the list
6. Type anything in the text field
7. Observe the text field
Expected results: Caret is aligned with the text
Actual results: Caret is aligned lower than the text
Reproducible in: 1.7.0, 1.8.0-pre.1, 1.8.0-pre.2 (2023.1.0a20, 2023.2.7f1, 2023.3.0b4)
Not reproducible in: 1.7.0, 1.8.0-pre.1, 1.8.0-pre.2 (2021.3.34f1, 2022.3.18f1, 2023.1.0a19)
Reproduced on: MacOS 13.5.2 (M1, 2020), Windows 11 Pro
Not reproduced on: No other environment tested
Notes:
- The same issue happens when adding a Binding Path to an action in the Input Actions Editor
- The regression is among the Editor versions themselves and not the Package versions
- The Input System Asset might get corrupted when changing versions (believably because of other package version errors)
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.