Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.1.X, 2021.2.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2022.1
Issue ID
1355591
Regression
No
The .uxml and all open .uss files get marked as dirty after modifying only one file
How to reproduce:
1. Open the attached '1355591.zip' project
2. In the Project window double-click on the Test Asset
3. In the UI Builder window add a new selector to the test1.uss
Expected result: Only the test1.uss gets marked as dirty
Actual result: The .uxml and all .uss files get marked as dirty
Reproducible with: UI Builder 1.0.0-preview.6 (2019.4.29f1, 2020.3.16f1), 1.0.0-preview.14 (2019.4.29f1, 2020.3.16f1, 2021.1.17f1), 2021.2.0b6, 2022.1.0a5
Cannot test with: 2018.4 (the package is not supported)
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a8
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b16
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.28f1