Leave site? Alert too aggressive when EditFlow and Custom Statuses is enabled.

[jomurgel]

Expected/Desired Behavior

Fill with either one:

The value of getPostEdits (wp.data.select('core/editor').getPostEdits()) would be empty until post save or unless the EditFlow status dropdown has changed.

Actual Behavior

After creating a new post, because of how the code changing the custom status

Edit-Flow/blocks/src/custom-status/block.js

Lines 20 to 42 in 2e07a1b

	subscribe( function () {
	const postId = select( 'core/editor' ).getCurrentPostId();
	if ( ! postId ) {
	// Post isn't ready yet so don't do anything.
	return;
	}
	// For new posts, we need to force the default custom status.
	const isCleanNewPost = select( 'core/editor' ).isCleanNewPost();
	if ( isCleanNewPost ) {
	dispatch( 'core/editor' ).editPost( {
	status: ef_default_custom_status
	} );
	}
	// If the save button exists, let's update the text if needed.
	maybeUpdateButtonText( document.querySelector( '.editor-post-save-draft' ) );
	// The post is being saved, so we need to set up an observer to update the button text when it's back.
	if ( buttonTextObserver === null && window.MutationObserver && select( 'core/editor' ).isSavingPost() ) {
	buttonTextObserver = createButtonObserver( document.querySelector( '.edit-post-header__settings' ) );
	}
	} );

is subscribed we immediately have a post edit (wp.data.select( 'core' ).getEntityRecordNonTransientEdits('postType', POST_TYPE, POST_ID )) which means that even if no changes were made when trying to leave the post or close the tab we are met with the "Leave site? Changes you made may not be saved." which is very confusing for editors.

Steps to Reproduce the Problem

1. Create post. Do nothing.
2. Attempt to close the tab or leave the page.
3. Confirm that the "Leave site?" alert is present.

(Optional) Additional notes

The solution may be to, if nothing has changed in the dropdown, add the default in PHP on post save (rest_pre_insert_${post_type} or on the save_post hook).