-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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: Move the BlockCanvas component within the EditorCanvas component #56850
Conversation
45256a3
to
a74c546
Compare
Size Change: +762 B (0%) Total Size: 1.72 MB
ℹ️ View Unchanged
|
? 'cursor: pointer; min-height: 100vh;' | ||
: '' | ||
}}}` | ||
}</style> |
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.
I moved this style tag to the "styles" object. (we do something similar in the post editor)
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.
Weirdly I can no longer replicate this. Apologies for the confusion.
@getdave You're saying it's ok right? |
Well there's clearly some e2e test failures. Let's see |
Ok I had inverted the condition to iframe the editor :) |
Flaky tests detected in 437b307. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7126565788
|
Related #52632
What?
In my quest to unify the post and site editor code bases, one of the steps is to unify the "canvas" of the editor. In this PR, I just move the
BlockCanvas
rendering to the unifiedEditorCanvas
component.In the process, it allowed me to remove the "dropzoneElement" prop but forced me to add some other temporary props (styles, iframeProps) which I hope to remove later with further unification.
Testing Instructions
Nothing really, just ensures the editors continues to render as before.