Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.71f1
6000.3.11f1
6000.4.0b12
6000.5.0a9
6000.6.0a1
Issue ID
UUM-137024
Regression
No
Quickly clicking "Open query in Search Window" in the Hierarchy twice opens the two Search tabs at the same time
How to reproduce:
1. Create a new Unity project
2. Near the Hierarchy Search, click the "Open query in Search Window" button twice
3. Observe the results
Expected results: Only one Search window opens
Actual results: Two Search windows open
Reproducible with: 6000.0.71f1, 6000.3.11f1, 6000.4.0b12, 6000.5.0a9, 6000.6.0a1
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
Note: When opening the Search with some delay, it reopens the Search instead opening a second window
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
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, and in this case, we found that this is a long-standing behaviour that also exists in the legacy hierarchy. Because this behaviour has been established for a long time and currently causes minimal user friction, we have decided not to change it.
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, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, and in this case, we found that this is a long-standing behaviour that also exists in the legacy hierarchy. Because this behaviour has been established for a long time and currently causes minimal user friction, we have decided not to change it.
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.