Search Issue Tracker
Fixed
Votes
0
Found in
6000.0.49f1
6000.1.3f1
6000.2.0b1
Issue ID
UUM-105716
Regression
No
USS files are not marked as dirty when an element is added to the Hierarchy
How to reproduce:
1. Open the "UIToolkitBugsBundle.zip" project
2. Open the "UIDocument.uxml" in UI Builder
3. In UI Builder, add any element to the Hierarchy
4. Observe the UI Builder
Expected result: UI Builder, UXML and USS files are marked dirty
Actual result: UI Builder, UXML file are marked dirty, USS files are not marked dirty
Reproducible with: 2023.1.0a18, 6000.0.49f1, 6000.1.3f1, 6000.2.0b1
Couldn’t test with: 2022.1.0a1, 2022.3.62f1, 2023.1.0a17 (only the UI Builder window gets dirty)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- The USS files are marked dirty after adding a second element
- After adding an element or multiple and saving changes, adding just one element will mark USS files as dirty
- If the UI Builder is closed, the issue will once again be reproducible
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
Fixed by another internal issue: UUM-105717: USS files are marked dirty when changes are made to the UXML file