Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.71f1
6000.3.12f1
6000.4.1f1
6000.5.0b1
6000.6.0a1
Issue ID
UUM-138289
Regression
No
Search query block sticks to cursor when dragged slightly and released in Query Builder Mode
Steps to reproduce:
- Create a new project using Universal 3D template
- Open the Global Search Window (Ctrl+K)
- In the Search Field enter string "count\{p:a:assets}"
- Make sure Query Builder Mode is on (F1)
- Click and hold on the yellow "area Assets" block
- Drag it a bit to the side and release
- Observe whole block goes back to place
- Hover the cursor over the yellow "area Assets" block
- Move the cursor and observe
Actual results: The yellow query block visually sticks to the cursor and follows it without holding the mouse button down. An additional click is required to detach it
Expected results: The query block does not stick to or follow the cursor
Reproducible with versions: 2023.1.0b1, 6000.0.71f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0b1, 6000.6.0a1
Tested on (OS): macOS 26.3, Ubuntu 24.04
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
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.6.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.