You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe.
We currently listen for direct clicks on the publish button to know when to run our checks. This means the shortcut will never fire anything from us. We would either need to add this or refactor our save listener to be more inline with how Gutenberg works (like listening for isSavingPost)
Just to leave a comment to summarize discussion - it surprises me that GB fully updates a post with the keyboard shortcut instead of doing an autosave, probably because of my habits from the classic editor. I am having a hard time finding the decision being made for the block editor - we can double check to see if that's on purpose but I wouldn't be aiming to change it on that front at this point. Definitely seems like rethinking the save listener is the correct route.
Is your enhancement related to a problem? Please describe.
We currently listen for direct clicks on the publish button to know when to run our checks. This means the shortcut will never fire anything from us. We would either need to add this or refactor our save listener to be more inline with how Gutenberg works (like listening for
isSavingPost
)Additional links
Link to the thread can be found here.
The text was updated successfully, but these errors were encountered: