Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.55f1
6000.2.0b13
6000.3.0a5
6000.4.0a1
6000.5.0a1
Issue ID
UUM-114382
Regression
No
Adding bindings to MultiColumnView breaks columns
Steps to reproduce:
- Open the UI Builder
- Add a MultiColumnListView from the Library pane
- Select the new MultiColumnListView if it is not already the case
- From the inspector, add a column in the Columns dropdown
- From the inspector, right-click on the tooltip property
- Add a binding to the field from the context menu
- In the Binding window, click the Ok button to create the binding
- Look at the UXML preview
Actual results:
The <Columns> tag is inside the <Bindings> tag.
Expected results:
The <Columns> tag is a sibling of the <Bindings> tag.
Reproducible with versions: 6000.3.0a5
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
Notes:
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
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
- Streaming is misspelled as "Steaming" in "Enable GPU Streaming" and "Enable Disk Streaming" tooltpis
- "IndexOutOfRangeException" thrown when moving caret left at start of TMP Input Field with rich text
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.5.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.