-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Editor: Fix 'isEditedPostAutosaveable' selector return value #70888
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Size Change: +17 B (0%) Total Size: 1.89 MB
ℹ️ View Unchanged
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Thanks for the review, @swissspidy! |
…ss#70888) Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: swissspidy <swissspidy@git.wordpress.org>
What?
Related #68680.
PR fixes the return value of
isEditedPostAutosaveable
selector when a post type doesn't supportautosave
.Why?
The selector is used by
AutosaveMonitor
and was providing it with a false value.Testing Instructions
wp.data.select( 'core/editor' ).isEditedPostAutosaveable()
Testing Instructions for Keyboard
Same.