Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.64f1
6000.2.15f1
6000.3.2f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-130518
Regression
No
Numeric property drag cursor gets enabled in the Inspector Preview window when the window is above numeric properties
Steps to reproduce:
- Create a new Unity project using a 3D Universal Template
- In the Hierarchy, create a "Text - TextMeshPro" GameObject
- In the Inspector, drag the "Layout Properties" window upwards, so that it covers some numeric properties
- In the "Layout Properties" window, hover over space where the covered property would approximately be positioned
- Observe the cursor
Actual results: The cursor detects the numeric value covered by the Preview window, and becomes the cursor with arrows (does not change the values, though)
Expected results: The cursor remains as is, since no properties are editable in the Preview window
Reproducible with versions: 6000.0.64f1, 6000.2.15f1, 6000.3.2f1, 6000.4.0b1, 6000.5.0a3
Tested on (OS): Windows 11, macOS 26.1 (M1 Pro)
Notes:
- Reproducible with "Default UI Material", "Layout Properties", "Intercepted Events", "RawImage" and "Button" preview windows (could not find more for testing)
- Can be reproduced with any UI GameObject
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
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 (6000.5.X):
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.