Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.28f1
2022.3.4f1
2023.1.3f1
2023.2.0a20
2023.3.0a1
Issue ID
UUM-41815
Regression
No
Special symbols can not be used when using them in the Binding Path of a UI Element property
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/NewUXML Template.uxml” asset
3. In the UI Builder Window, in the Hierarchy Tab, select “Button”
4. In the Inspector Tab, in the “Binding Path” Property, type “>” or other special symbols
Expected result: Symbol is typed
Actual result: A warning is displayed, stating that such symbols can not be entered
Reproducible with: 2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a8
In 2023.2.0a9 and higher and 2023.3, it is only reproducible with UxmlTraits. The warning was lost with UxmlSerialization and needs to be brought back.
Reproducible on: Intel MacOS 13.4
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
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not always matching search term correctly
- Crash on memcpy when opening a project that loads TSS files
Resolution Note:
The warning was removed in recent versions of Unity (2023.2 and higher). So it is now possible to input ">" in the editor binding path.