Skip to content
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

List Jetpack Blocks after Core blocks when searching blocks in "Add Block" sidebar or Slash Inserter popup menu #17732

Closed
mrwweb opened this issue Nov 6, 2020 · 1 comment
Labels
[Focus] Blocks Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack

Comments

@mrwweb
Copy link

mrwweb commented Nov 6, 2020

Is your feature request related to a problem? Please describe.

When searching for blocks using the "Add Block" sidebar or slash inserter, Jetpack blocks are listed before core blocks.

This is extremely annoying for common blocks like "Image". It's not that the Jetpack blocks aren't useful, but they are so clearly not the most likely block needed for a search like that. I've personally found that this behavior is making me wish I just didn't have Jetpack blocks at all.

Describe the solution you'd like

List Jetpack blocks second in the slash inserter and "Add Block" sidebar with a possible exception for exact matches on the block name. (I imagine that the Jetpack block would be the only block for exact name matches in most cases.)

Additional context

Slash Inserter search for "image":
image

Add Block sidebar search for "image":
image

Interestingly, the contextual add block button search for "image" does not display this behavior:
image

@jeherve jeherve added the [Focus] Blocks Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack label Nov 9, 2020
@jeherve
Copy link
Member

jeherve commented Nov 9, 2020

Yeah, I agree this is frustrating. Unfortunately, that's not something we can fix from within the Jetpack plugin. We do not control the order of the blocks in the inserter. This is done by the block editor, and right now it seems to place blocks created by third-parties above core blocks for some reason. This is true with any plugin. I'm not sure if this is done on purpose, or if that is a bug.

I see it's been reported in the Gutenberg repo here:
WordPress/gutenberg#26651

I'll add a comment about your report to that issue. I would recommend subscribing to that issue to see where things go from here.

I'll be closing this issue, since that's not something we can fix in Jetpack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Blocks Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack
Projects
None yet
Development

No branches or pull requests

2 participants