Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.36f1
2021.3.5f1
2022.1.7f1
2022.2.0a17
2023.1.0a2
Issue ID
UUM-8020
Regression
No
UIToolkitWindow's menu is not clearly visible in Light Theme when working with Graph View
To reproduce:
1. Open the project “IN-9206_UnityBugs”
2. Make sure the Editor is in Light Mode
3. Open the UIToolkitWindow (Window → UI Toolkit → UIToolkitWindow)
Expected result: The UIToolkitWindow’s menu is clearly visible
Actual result: It is hard to see some menu buttons
Reproducible with: 2020.3.36f1, 2021.3.5f1, 2022.1.7f1, 2022.2.0a17, 2023.1.0a2
Reproduced on: macOS 12.4 (Intel)
Notes:
· The menu is clearly visible with Dark Theme
· The menu is clearly visible when GraphView is not used (To disable it comment two last lines in UIToolkitWindow.cs script)
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 bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue, the number of users affected by it and it’s current experimental state. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2023.1.X):
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue, the number of users affected by it and it’s current experimental state. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.