Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.3.0a3
Issue ID
UUM-112235
Regression
No
Selected setting is not fully marked in the "Add Settings" modal
Steps to reproduce:
- Create a project
- File -> Build profiles
- Select the platform and click "Add Build Profile"
- Leave the default proposed build title and click "Add Build Profile"
- Verify that the new build is created and you get its data in the build details window
- Click "Add Settings"
- Select any item from the list
Actual results: The selection markup is presented over most of the line, leaving a small portion unmarked
Expected results: The markup must be displayed across the entire line
Reproducible with versions: 6000.3.0a2, 6000.3.0a3
Not reproducible with versions: -
Can’t test with versions: 6000.3.0a1: "Add Settings" functionality is added only from the 6000.3.0a2 build.
Tested on (OS): M1 Max - Sequoia 15.5
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:
This is a cosmetic issue that poses a risk of performance regression. The additional spacing is caused by the scrollbar, which may or may not be visible depending on the content. Currently, we lack a reliable method to determine whether the scrollbar will be displayed.
This issue also occurs when using the Add Component menu and has been a known limitation for an extended period. Given the complexity of implementing a proper fix without potential side effects, I am marking this as "Won't Fix."
We plan to address this issue when we upgrade the dropdown component to use UI Toolkit, which will provide better handling of dynamic scrollbar visibility.