-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Gutenboarding: remove save text node override in the block editor #42508
Conversation
… not sure of the mechanism behind the error, but the page fails when React attempt to unmount components. It's looking for a precise node tree it appears.
This PR does not affect the size of JS and CSS bundles shipped to the user's browser. Generated by performance advisor bot at iscalypsofastyet.com. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Saving, publishing and launch flows working as expected.
We have other things we should fix up about the editor overrides for unpublished posts (e.g. we're changing the publish confirmation button to a tertiary style) but this fixes the crash.
And leaving the button as "Update" for published posts isn't too bad. I know it was a very conscious decision to change it to save, but at least "Update" isn't completely wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! This resolves the issue for me, and the launch flow is still working as expected.
Thank you, @p-jackson and @andrewserong once again for your continued service to the cause |
Changes proposed in this Pull Request
Create a site with Gutenboarding at
/new
Now try to create and publish a new post or page.
You can't, can you?
Do you see this?
It's because we're manipulating the buttons in the editor's header, specifically the text node in the publish button.
Let's not replace the text node as React does not like it at all. I'm not sure of the mechanism behind the error, but the page fails when React attempt to unmount components. It's looking for a precise node tree it appears.
props to @ianstewart for finding this bug and giving us something do
Testing instructions
Code to patch in D43745-code