-
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
Inserter: Inner blocks not inserted at correct location #24403
Comments
Also reported in #24501. This seems like something important to fix for WordPress 5.5.1. |
Is there a filter to show more than 6 blocks (like in block variations, which show all variations available)? This could be a quick fix for now. |
The Is this related? |
Is this making it to 5.5.1? |
If Prop is cached, it seems to be inserted at correct location. please try https://github.com/WordPress/gutenberg/tree/try/issue-24403 |
Seeing the same issue that @chvillanuevap mentions above, but wanted to mention that I'm seeing this behaviour:
It seems adding a min-height to the InnerBlocks element makes this work consistently (broken) for me. |
I just wanted to add that this behavior not only applies to blocks, but also block patterns. |
#26281 reported the same issue for patterns. |
Hey: I wrote the following on the forum on WordPress.org. The Gutenberg editor looses location of add (+) clicked in the content area, if ‘Browse all’ clicked. I use Group block a lot. It seem to happen a lot when I click within the Group block. The problem is not limited to Group block. Example: Thanks for a great editor. Phil |
I've had to step away from this. Feel free to pick up #26443 and finish it or to use it as inspiration for a different approach. |
Same error con WP 5.7.2 |
Blocks may not be inserted in the correct location when using the following steps:
Visual flow
Setup
Click appender to access quick inserter
Click "Browse all" to access the main inserter
Pick a block from the main inserter
The block is not inserted where the appender was clicked
Context
I believe this is the same issue as described in #24262. #24285 closed that issue, but it appears to have addressed an insertion bug in top level blocks, not in inner blocks.
Editor version:
Related: #24402
The text was updated successfully, but these errors were encountered: