Search Issue Tracker
Fixed
Fixed in 6000.0.52f1, 6000.1.8f1, 6000.2.0b6, 6000.3.0a1
Votes
0
Found in
6000.0.49f1
6000.1.3f1
6000.2.0b1
6000.3.0a1
Issue ID
UUM-104904
Regression
Yes
USS code is not updated when a selector is deleted or is moved to a new USS file
How to reproduce:
1. Open the “UIToolkitBugsBundle.zip“ project
2. Open the “UIDocument“ in UI Builder
3. Expand both USS files in the StyleSheets tab
4. Drag the “.Selector1“ selector to another USS file
5. Select the “1class.uss“ header in StyleSheets tab
6. Observe the USS Preview at the bottom of UI Builder
Expected result: The USS preview is empty
Actual result: The USS preview contains the definition for “.Selector1“
Reproducible in: 6000.0.41f1, 6000.0.49f1, 6000.1.3f1, 6000.2.0b1
Not reproducible in: 2022.3.62f1, 6000.0.40f1
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Workaround: Rename any one selector from each affected USS file (or update the selector in any way)
Notes:
- As a result, this makes the UI Builder falsely duplicate a selector when the project or the UI Document are reopened
- There have to be at least 2 USS files added to the UI Document
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment