Repository navigation
Editor shows "changes were not saved" / leave-page warning even after a successful save #79776
Description
Sharing feedback from WordPress.com users (via our in-product surveys) about a false unsaved-changes warning.
What users expect: after a successful save, closing the post or navigating away shouldn't warn that changes weren't saved.
What happens: users report that even right after saving, they get a "changes were not saved" message when they close the editor, and a leave-page warning fires on every navigation despite having just saved.
when I save an article then I close it, I get the message "changes were not saved".
Every time I leave a page (even if I just save) it tells me I'm leaving the page without saving.
Activity
Mamaduka commentedon Jul 1, 2026
Could be related to #78989. Worth re-testing once WP 7.0.1 ships.
cc @annezazu
annezazu commentedon Jul 2, 2026
Very much feels related to that prior fix. Agreed around re-testing post 7.0.1. Please do report if this issue continues to occur or come up from users @gracie.
github-actions commentedon Aug 2, 2026
Hi,
This issue has gone 30 days without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest versions, you can help the project by responding to confirm the problem and by providing any updated reproduction steps.
Thanks for helping out.
github-actions commentedon Sep 6, 2026
Hi,
This issue has gone 30 days without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest versions, you can help the project by responding to confirm the problem and by providing any updated reproduction steps.
Thanks for helping out.
youknowriad commentedon Sep 28, 2026
Re-tested on WP 7.1.2 with Gutenberg: after saving (⌘S) or publishing, the post is no longer dirty and navigating away shows no "changes not saved" warning. With genuinely unsaved edits the warning still appears as it should. I recall that we solved a few related issues recently. so I'm closing this one.