Search Issue Tracker
Won't Fix
Won't Fix in 6000.3.X, 6000.5.X
Votes
3
Found in
6000.0.42f1
6000.1.0b10
6000.2.0a6
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-100294
Regression
No
MultiColumnListView Columns have the same Name value when binding with Localization
Reproduction steps:
1. Open the attached “IN-96987.zip” project
2. Double click on the “Document.uxml” from the Project Window
3. In the UI Builder Hierarchy select the MultiColumnView
4. In the Inspector find the Columns property and expand it
5. Observe the Name property of both Columns
Expected result: Column names are “Column 1” and “Column 2”
Actual result: Both Column Names are the same (“Column 1”)
Reproducible with: 1.5.2, 1.5.4 (6000.0.41f1, 6000.1.0b11, 6000.2.0a7)
Couldn’t test with: 1.5.4 (2022.3.60f1) (Could not downgrade)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
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 planned to be addressed in a future refactor of the UI Builder inspector. For now, this is a known limitation.
Resolution Note (6000.5.X):
This is planned to be addressed in a future refactor of the UI Builder inspector. For now, this is a known limitation.
Resolution Note (6000.3.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.