-
Notifications
You must be signed in to change notification settings - Fork 4.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
Editor: Remove extra div container and unify the container between post and site editors #62016
Conversation
…st and site editors
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. |
Size Change: -2.55 kB (-0.15%) Total Size: 1.74 MB
ℹ️ View Unchanged
|
Flaky tests detected in 4c37ff7. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/9252326076
|
Something isn't right here: meta.mp4When editing a long post the metabox appears to be floating in the middle of it, and the post styles (background color at least) disappear beneath it. |
Good catch @jameskoster I think I fixed it in the last commit. |
…st and site editors (WordPress#62016) Co-authored-by: youknowriad <[email protected]> Co-authored-by: jameskoster <[email protected]>
…st and site editors (WordPress#62016) Co-authored-by: youknowriad <[email protected]> Co-authored-by: jameskoster <[email protected]>
What?
Small refactoring PR that removes and unifies
edit-post-visual-editor
andedit-site-visual-editor
containers. There's already a sharededitor-visual-editor
container. So this PR removes that extra DOM node and moves some styles around. I'm keeping the classnames mostly for backward compatibility though.Testing Instructions
1- Ensure that the editor looks properly with and without metaboxes (with and without iframe).
2- Ensure that the site editor looks properly.
3- Ensure that stylebook looks properly.