Skip to content

Autosave continues to trigger for published posts when no changes applied #12318

@gziolo

Description

@gziolo

Describe the bug

I discovered that autosave triggers even when there were no changes applied only for the published post. It works perfectly fine for drafts.

To Reproduce
Steps to reproduce the behavior:

  1. Create a post (it isn't related to demo post only), write some content and publish it.
  2. Reopen your published post.
  3. Open network tab in your browser's developer tools.
  4. Change something in one of the blocks.
  5. Observer autosave being triggered after your changes were autosaved.

Expected behavior
Autosave is triggered only once after content in the published post has changed.

Screenshots
autosave-published-post

Desktop (please complete the following information):

  • OS: macOS Mojave
  • Browser: Chrome
  • Version: 70

Metadata

Metadata

Assignees

Labels

[Feature] Writing FlowBlock selection, navigation, splitting, merging, deletion...[Type] BugAn existing feature does not function as intended

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions