Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.61f1
6000.0.48f1
6000.1.1f1
6000.2.0a10
Issue ID
UUM-104217
Regression
No
[Ubuntu] Mouse cursor is set box select mode after exiting VFX Graph's Rename Context function
*Steps to reproduce:*
# Open the attached project
# Open the New VFX asset
# Double-click on the TestContextField to enter Context Rename mode
# Modify the name
# Click outside the text field to exit rename mode, don't hold the mouse button
# Move the mouse around without clicking or holding
*Actual results:* If clicked on the node, moving the mouse will drag the node around. If clicked outside the node, moving the mouse creates a box selector. It behaves like the mouse button is held down.
*Expected results:* Moving the mouse does not move the node or start box selecting, until the user clicks and holds the mouse button.
*Reproducible with versions:* 2022.3.61f1, 6000.0.48f1, 6000.1.1f1, 6000.2.0a10
*Reproducible on (OS):* Ubuntu 24.04, Ubuntu 22.04
*Not reproducible on (OS):* Windows 11, macOS 15.4.1
*Notes:*
* Issue does not reproduce if the name was not changed
* There is a progress window that appears for a very short time after renaming the text that might have something to do with this.
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
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.