-
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
core/button
variations doesn't appear in core/buttons
inserter
#53498
Comments
Hi @petitphp, thanks for reporting this issue. You will need to add
That said, there is another issue where Let me know if I can answer any additional questions or if this can be closed. Thanks! |
@ndiego Thanks for the answer. I was expecting to see the variation show up in the inserter like with the "Social links" blocks. Do you think we could we have the same behavior between the two blocks ? |
I'm seeing that the "buttons" block has this flag for its inner blocks I think personally that it's reasonable to expect the inserter to show all the variations and override the "direct insert" config if there are multiple possible variations/blocks as child blocks. |
* Buttons Block: Show inserter if button have variations (#53498) * Combine `useSelect` variations with the existing one * Add comment about the custom check for the `directInsert` option value that should be handled in the `Inserter`
Description
Variation of
core/button
block are not available in thecore/buttons
inserter.I expect to see the variations when adding button.
Step-by-step reproduction instructions
Only the basic block "button" is available, the variations can't be used.
wp.blocks.getBlockVariations('core/button');
The two registered variations are correctly listed as a result.
Screenshots, screen recording, code snippet
Small code snippet to demonstrate the issue.
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: