Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.2.0a15
2020.2.0a16
Issue ID
1255998
Regression
No
The Editor's 'hasUnsavedChanges' functionality loses changes when at least one change is invalid
How to reproduce:
1. Open attached project "hasUnsavedChangesInvalidChanges.zip" and scene "SampleScene"
2. Open Profiler Window
3. Click on Profiler Modules drop-down list and click on the settings icon
4. Click "Add" button two times and don't change the name of the modules created
5. Click "Add" button one time and change the name of the created module to unique
6. Close Profiler window and press Save
5. Observe Profiler Window
Expected result: Correct profiler changes are saved
Actual result: None of the profiler changes are saved
Reproducible with: 2020.2.0a15
Cannot test with: 2018.4.23f1, 2019.4.0f1, 2020.1.0b13, 2020.2.0a14 - (functionality added to the EditorWindow in 2020.2.0a15)
Note: The hasSavedChanges API does not support the ability to cancel the window's close request in the event of a failure to save
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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b2