-
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
Remove experimentalUIParts API #20979
Conversation
Size Change: -163 B (0%) Total Size: 857 kB
ℹ️ View Unchanged
|
Do you know the initial commit that introduced it? It’d make it easier reviewing 😃 Code looks good but I might overlook something. |
I'm merging this now, We can revert it if there's feedback suggesting it's still important. |
Thanks @youknowriad! I haven't really kept up with G2, would you have any pointers as to how we can disable the block toolbar now? 😅 (That's what we were using |
A bit late. This is the first I'm coming across this after tracking it down as the cause of this issue: Automattic/wp-calypso#42031 (review)
What were the motivations for removal? Can we restore this functionality? |
Experimental UI parts api was dropped in WordPress/gutenberg#20979 Remove usage and hide via CSS
* fix(deps): update wordpress monorepo * Deduplicate @WordPress packages * Remove block toolbar via CSS Experimental UI parts api was dropped in WordPress/gutenberg#20979 Remove usage and hide via CSS Co-authored-by: Renovate Bot <[email protected]> Co-authored-by: Jon Surrell <[email protected]> Co-authored-by: Sergio Cinos <[email protected]>
I just chatted with @youknowriad. He told me that Gutenberg folks are generally opposed to keeping an experimental API that isn't used in the project itself and where the use-case is not very wide for third-party plugins. He had an alternative suggestion though: Hide the block toolbar for blocks that don't have any block controls, and that live inside a locked template (such as). We're both not entirely sure if we'd inadvertently prevent any other block interactions that way, but agreed that it might be worth exploring in a PR and soliciting feedback that way. |
This PR removes the experimentalUIParts API as this became useless with the G2 refactoring.
cc @ockham