Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.45f1
2022.3.52f1
6000.0.26f1
6000.1.0a3
7000.0.0a8
Issue ID
UUM-86733
Regression
No
Matching Game View creates unsaved changes even though nothing to save
*Steps to reproduce:*
# Open a Unity Project
# Create a new UI Document in the Project Window via Right-Click > Create > UI Toolkit > UI Document
# Open the new UI Document in UI Builder by double clicking on it
# In the UI Builder Hierarchy, select the .uxml file. The Inspector should show the Canvas Size settings
# Check the box next to 'Match Game View'
*Actual results:* The UI Builder Window detects unsaved changes and the Unsaved Changes Marker ( * ) is displayed.
However, nothing actually needs to be saved as changing the Canvas Size is auto saved in the Library (not on the uxml asset itself), and if you change the Canvas Size any other way (such as 'Fit Canvas' button or manually setting the values), then there is no unsaved changes.
If you try to exit the UI Builder Window, you will get an 'Unsaved Changes Detected' warning. However, pressing either Save or Discard will not affect anything as there are no changes to save, and even if you press Discard the Canvas Sizes and Match Game View checkbox will have been auto saved.
*Expected results:* The UI Builder Window does not detect unsaved changes when the 'Match Game View' box is ticked.
*Reproducible with versions:* 6000.1.0a3, 6000.0.26f1, 2022.3.52f1, 2021.3.45f1
*Not reproducible with versions:* -
*Can’t test with versions:* -
*Tested on (OS):* Windows 10/11
*Notes:* -
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
- Property fields overlap in the Override window when comparing changes
- "Timeflow Animation System" custom package appears twice in the Package Manager
- Sprite Atlas Override for iOS setting remains disabled when saving its change to enabled
- Increased Memory usage when Update Mode 'On Demand' Realtime lights are used and DX12 API is selected
- Shader warnings in URP ShaderGraph when using the Normal From Texture node
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.