Search Issue Tracker
Fixed
Fixed in 1.8.0
Votes
0
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-797
Regression
Yes
Canceling an unsaved input actions window removes the "*" unsaved asset symbol even if the changes are still unsaved
Reproduction steps:
1. Open the attached project “SaveSymbol”
2. In the Project window double click the “Assets/New Controls.inputactions” Input Actions asset to open Input Actions Editor window
3. Turn off the Auto-Save function
4. Make some changes to the asset
5. Close the window
6. In the Save Asset prompt window press the “Cancel” button
7. Observer the title of the Input Actions Editor window
Expected result: The window title is: “(*) New Controls (Input Actions)”
Actual result: The title of the window is: “InputActionsEditorWindow”
Reproducible with: 1.8.0-pre.2 (2022.3.20f1, 2023.2.11f1, 2023.3.0b8)
Not reproducible with: 1.7.0 (2021.3.35f1, 2022.3.20f1, 2023.2.11f1, 2023.3.0b8), 1.8.0-pre.1 (2021.3.35f1, 2022.3.20f1, 2023.2.11f1, 2023.3.0b8)
Reproducible on: macOS 13.6.4 (Intel)
Not reproducible on: No other environment tested
Notes:
- The Save Asset prompt doesn’t show up in 2021.3.35f1 with 1.8.0-pre.2 package version, but it saves the changes even if Auto-Save is disabled
- The changes stay unsaved and the prompt is given again when trying to close the window again
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.8.0):
This issue have been fixed in a pending PR. The problem was incorrect transition of state between editor windows when a new window was created inheriting state from the window being closed.