Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.3.0a1
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-110425
Regression
No
UI Builder Filter Values have no bounds
Steps to reproduce:
1. Create a new project
2. Create UI Document (Create > UI Toolkit > UI Document)
3. Double-click on the newly created UI Document to open UI Builder
4. Drag Visual Element to the Hierarchy
5. Open Filter dropdown section in Visual Element Inspector
6. Add Opacity filter and change its value by dragging it to the left
Actual results: Value goes to negative and no changes are made visually
Expected results: Value goes no lower than 0
Reproducible with versions: 6000.3.0a1
Couldn’t reproduce with versions: 2021.3.52f1, 2022.3.62f1, 6000.0.52f1, 6000.1.9f1, 6000.2.0b7 (no Filter section)
Tested on (OS): Ubuntu 22.04, macOS Sequoia 15.4 (M4)
Note: Issue is also reproducible on Invert, Grayscale, Sepia and Contrast filters as well
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
- The Up, Down and other Buttons in a Style Sheet's Inspector unselect items when they are clicked while they are disabled
- Virtual Player remains active and still launches when removed from Additional Editor Instances from a custom Play Mode Scenario
- UI Toolkit Editor Window Creator becomes not interactable and greyed out when a long name is entered
- [Web][iOS] Web Player keeps restarting on launch when Native C/C++ Multithreading is enabled
- "Add Scene to Scenes in Build" pop-up reappears after Scene has already been added and another Multiplayer Editor Instance is loaded
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.