Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.15f1
Issue ID
UUM-77857
Regression
Yes
[WinArm] UI Toolkit Inspector "Bindings" section sometimes disappears when moving Visual Element around Viewport
How to reproduce:
1. Create a new Unity project
2. In the Project window, Create -> UI Toolkit -> UI Document
3. Open the UI Document and create a "Button" Visual Element
4. Select the "Button" and, in the Inspector, go Position -> Position Mode -> Absolute
5. Drag the "Button" around the "Viewport"
Expected results: Moving around the "Button" doesn't affect the Inspector
Actual results: Moving around the "Button" makes the "Bindings" section collapse resulting in flickering in the Inspector
Reproducible with: 6000.0.15f1
Not reproducible with: 2021.3.42f1, 2022.3.42f1
Reproducible on: Windows 11 (Arm)
Not reproducible on: Windows 11 (x86), macOS 14.5 Sonoma (M1) (The other flickering bug occurs here, might not be related to this)
Note: Not looking for regression since not all versions are available for Arm devices
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.