Search Issue Tracker
Fixed in 2022.2.16f1
Fixed in 2022.2.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0b5
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.1.12f1
2022.2.0b5
2022.3.16f1
2023.1.0a6
2023.2.0a1
2023.3.0b3
Issue ID
UUM-12413
Regression
No
Line breaks do not work when adding them to UITextSettings
Reproduction steps:
- Open the user's attached project
- Open Game view and observe the “。” symbol
- Open Assets > UI > UXMTemplate
- In the UI Builder Hierarchy select TextElement
- In the UI Builder Inspector edit text > size
- Observe Game view
Expected result: Line breaks are in the end of the line
Actual result: Line breaks are ignored
Reproduced with: 2020.3.38f1, 2021.3.8f1, 2022.1.12f1, 2022.2.0b5, 2023.1.0a6
Reproducible on: macOS 12.4 (Intel)
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
- "Report is from another project" popup warning is shown on domain reload when Project Auditor was previously ran in a different project
- Addressables Analyzer flags duplicate resource references from ScriptableObjects incorrectly when the corresponding field has been removed
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
Resolution Note (fix version 2023.3):
Ensuring UnicodeLineBreakingRules are applied to text.
Resolution Note (fix version 2023.2):
Ensuring UnicodeLineBreakingRules are applied to text.
Resolution Note (fix version 2023.1):
Fixed Editor LineBreakingRules
Resolution Note (fix version 2022.3):
Ensuring UnicodeLineBreakingRules are applied to text.