-
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
Block Manager: Make it a private component in the block editor package #67255
Conversation
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: +110 B (+0.01%) Total Size: 1.82 MB
ℹ️ View Unchanged
|
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.
Block hiding from preferences works as expected, but I think the CSS isn't being applied to the list
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.
Thanks for the changes!
I tested in site and post editors.
No regression in UI or behaviour in my testing.
Thanks for the review!
I researched this and found the following. Are these behaviors correct?
In any case, it's not related to this PR, so I would like to merge it. |
@ellatrix would know best, maybe there are reasons that force us to load "content.css" in the root document but conceptually it's not really meant for the root document and more for the iframe. |
BlockManager
component reusable #67052allowedBlocks
in blocks that support it #62703 (See this comment)What?
Regarding the block manager component:
editor
package to theblock-editor
package.Why?
This PR is needed to use the
BlockManager
component in the UI for allowedBlocks.From this comment:
How?
editor-block-manager
prefix has been replaced with theblock-editor-block-manager
prefix in bulk.Since the
BlockManager
component was not originally a publicly available component, there should be no backward compatibility issues even if the package is moved.My only concern is whether there are any plugins that rely on the
.editor-block-manager__
CSS classes to customize the "Manage block visibility" settings, but that doesn't seem to be the case with the WPdirectory results.Testing Instructions
The "Manage block visibility" setting should continue to work as before. Most of the functionality should be guaranteed by this E2E test.