Closed dennisbaum closed 1 year ago
Seems this behavior is intended. What does the team think? Should it be closed or improved?
I agree that ESC
should be treated as "Cancel" with the current implementation.
But with our planned refactoring of the structure field, every change inside a structure row will immediately be synced with the global content object of the whole page (meaning that saving changes in a structure entry is no longer needed). Discarding will then happen with the Unsaved Changes bar like with any other field. At this point the "Cancel" button will no longer be needed.
If i get you right, there is no need to save the structure field AND save the page after that planned refactoring? i would looove that! lots of editors (myself included) always forget to save twice.
Yep. You will be able to just leave the structure field and save the page.
so i will close that issue and looking forward to the new structure-field. thx!
Description
If i open a row of a structure field and change something in the detail-view, pressing ESC-Key closes the details BUT saves the changes to the structure-field. the status of the page is then dirty.
Expected behavior
I'd expect ESC to be the same as clicking on Cancel. The changes should not be saved. The status of the page should stay as before
To reproduce
Your setup
K3.7.5
Console output
no javascript error
Your system (please complete the following information)