Search Issue Tracker
Fixed
Votes
0
Found in
2022.3.60f1
6000.0.43f1
6000.1.0b11
6000.2.0a7
Issue ID
UUM-100560
Regression
No
Adding an existing .uss file makes it dirty
How to reproduce:
1. Create a new Unity project
2. In the Project window, right-click -> Create -> UI Toolkit -> UI Document
3. Open the UI Document and navigate to the StyleSheets tab
4. Create a StyleSheet, save it and then remove it
5. Click the "+" button -> Add Existing USS -> previously created StyleSheet
6. Observe the results
Expected results: The added .uss file is not dirty
Actual results: The added .uss file is dirty
Reproducible with: 2022.3.60f1, 6000.0.43f1, 6000.1.0b11, 6000.2.0a7
Reproducible on: macOS Sequoia 15.3 (M1)
Not reproducible on: No other environment tested
Note: In 2022.3 stream there seems to be no indication of unsaved changes on the .uss header but it seems to be reproducible there
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
- 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
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-49819