Search Issue Tracker
By Design
Unknown (hidden) 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X
Votes
0
Found in
2020.3.35f1
2021.3.4f1
2022.1.4f1
2022.2.0a16
2023.1.0a1
Issue ID
UUM-4632
Regression
No
USS style selector shows the wrong Wrap enabled when the default Wrap is being used
Reproduction steps:
1. Open the attached “USSTextWrap” project
2. Open the “MyUXML“ asset in UI Builder
3. Select the “Label#foo“ selector (StyleSheets > MyUSS.uss > Label#foo)
4. Observe the enabled Wrap (Inspector > Text > Wrap)
5. Observe how the “foo” Label is wrapped in Viewport
Expected result: The selector shows its true default Wrap
Actual result: The selector shows that its Wrap is “normal”, even though “nowrap” is used
Reproduced with: 1.0.0-preview.18 (2020.3.35f1), 2021.3.4f1, 2022.1.4f1, 2022.2.0a16
Reproduced on: macOS 12.0.1 (Intel), Windows 10
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
- [Scene View][Ubuntu] Prefab mode UI ghosting in HDRP
- Deleting AudioMixer asset throws MissingReferenceException and breaks the Audio Mixer window
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
Resolution Note:
Hi!
This is working as intended. When you select a selector, the inspector will show all the available properties that you can add to that selector. A new selector will not have any properties set from the start.
When a property is set in a selector, you should see a white override bar for that property. When it is set, you will also see it appear in the uss preview window. Unless you see the white bar or see the property in the preview window, that property is not set as part of the selector. Since it's not part of the selector, the value displayed in the inspector does not matter (it's not being applied in any way, shape or form).
If you want to see the actual computed value, you will need to look at the #foo element.
That being said, we are aware this workflow is confusing for people who are not aware of the "under the hood" details. We've made some improvements to clarify this in recent versions of Unity and we have more improvements coming as well.
Thanks!