-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Block Editor: remove usage of Emotion #73799
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
base: trunk
Are you sure you want to change the base?
Conversation
|
Size Change: -10.1 kB (-0.39%) Total Size: 2.57 MB
ℹ️ View Unchanged
|
|
Flaky tests detected in 59bc5be. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/19973281267
|
aduth
left a comment
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.
|
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @CreativeDive. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. 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. |
| @@ -0,0 +1,3 @@ | |||
| .single-column { | |||
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.
This would also be the first usage of CSS modules in block-editor. I wonder if we should refrain at the moment and stay with regular SCSS in this package (it's ok for components and ui)


Removes a single usage of Emotion in the Block Editor package, which caused the
block-editorscript to bundle the library independently fromcomponents. That led to two instances being active in the WordPress block editor environment.All we did use Emotion for was a single
grid-columnstyle that ensures that the two inputs inWidthHeightControlare displayed side-by-side, in two columns:This fixes #72558 as there will be only one Emotion instance remaining, in
components.