When opening an entry, the Save button is correctly disabled because there are no unsaved changes.
After modifying any field, the Save button becomes enabled, which is expected.
However, after saving the changes successfully, the Save button remains enabled instead of becoming disabled.
The dirty state also behaves incorrectly. If I change a value from A to B, save it, and then change it back to A, the Save button becomes disabled even though the last saved value is B.
It looks like the form is still comparing changes against the values that were loaded when the page was opened, instead of the values from the last successful save.
Steps to reproduce
- Open any entry in the admin.
- Verify that Save is disabled.
- Change any field.
- Verify that Save becomes enabled.
- Click Save and wait for it to complete.
- Notice that Save is still enabled.
- Change the field back to its original value from before the first edit.
- Notice that Save becomes disabled, even though the current value differs from the last saved value.
Expected behavior
After a successful save, the current values should become the new baseline. The Save button should be disabled until another change is made.
Actual behavior
The form continues to compare changes against the values from the initial page load instead of the last successfully saved values, causing the Save button and dirty state to behave incorrectly.
When opening an entry, the Save button is correctly disabled because there are no unsaved changes.
After modifying any field, the Save button becomes enabled, which is expected.
However, after saving the changes successfully, the Save button remains enabled instead of becoming disabled.
The dirty state also behaves incorrectly. If I change a value from A to B, save it, and then change it back to A, the Save button becomes disabled even though the last saved value is B.
It looks like the form is still comparing changes against the values that were loaded when the page was opened, instead of the values from the last successful save.
Steps to reproduce
Expected behavior
After a successful save, the current values should become the new baseline. The Save button should be disabled until another change is made.
Actual behavior
The form continues to compare changes against the values from the initial page load instead of the last successfully saved values, causing the Save button and dirty state to behave incorrectly.