Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.3.7f1
6000.4.0b7
6000.5.0a6
6000.6.0a1
Issue ID
UUM-133757
Regression
Yes
"Value" input field exceeds filter area when entering large numbers in "Query Builder Mode"
Steps to reproduce:
- Create a new Unity project
- Click the "Search" icon next to the "Undo History"
- Turn on "Toggle Query Builder Mode"
- Click "+" in the search field
- Enter "age" into the search field
- Verify that the "Age" item is displayed in the search results list
- Select it
- Verify that the selected "Age" item capsule becomes displayed in the search field
- Click on an arrow in the capsule
- Enter "1111111111" instead of the default 1.5 value
- Observe the result
Actual results: The "Value" input field goes out of the filter area
Expected results: The "Value" input field should stay in the filter area
Reproducible with versions: 6000.3.0a2, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Not reproducible with versions: 6000.0.67f1, 6000.2.15f1, 6000.3.0a1
Tested on (OS): macOS - Tahoe 26.2
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.