Search Issue Tracker
Won't Fix
Votes
0
Found in
1.18.0
Issue ID
UUM-135142
Regression
No
Input Action Editor window toolbar buttons overlap each other when a Control Scheme with a long name is added
Steps to reproduce:
- Create a new Project using the Universal 3D template
- Open the Input Action asset (Assets/Assets/InputSystem_Actions.inputactions)
- Click on the All Control Schemes dropdown
- Click the "Add Control Scheme" button
- Enter a very long Scheme Name
- Click the "Save" button
- Make sure the Input Action Editor window is set to its minimum size and is not docked
- Observe the top toolbar of the Input Action Editor window
Actual results: The long Scheme Name causes other buttons in the toolbar to overlap each other
Expected results: No UI elements overlap
Reproducible with versions: 1.18.0 (6000.0.68f1, 6000.3.10f1, 6000.4.0b10, 6000.5.0a7)
Tested on (OS): MacOS Silicon Tahoe 26.2
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
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.
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.