You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One fairly common need is aligning more than one button in a row. Multiple block libraries have added similar tools (either a special multiple buttons block or the ability to add more instances in a single button block). We should explore bring this into core, likely leveraging child blocks for the extra buttons, but in a more convenient way than forcing people to add columns first to hold each button in place.
The text was updated successfully, but these errors were encountered:
YO! I passionately love this ticket, so I created a mockup:
The mockup above is inspired by efforts underway in #16897 (comment), where we are building a container for social links that show up side by side.
This would work the same for a Button Group or what the name might end up as.
As noted in that ticket referenced, this would make use of a new UI feature we'd build for parent block containers, to allow child block UIs to be absorbed by the parent.
This would work the same for a Button Group or what the name might end up as.
I hope we can call this just "Buttons". Another thing that this should also help with is that alignment controls move from the individual "Button" block (what we have right now) to the container "Buttons".
What if the Group block had a horizontal layout option? Using flexbox you could have a wide range of alignment/spacing controls, and you could use show several blocks (not just buttons) on the same line without having to use columns. (And with flex-wrap it would be easily responsive.)
One fairly common need is aligning more than one button in a row. Multiple block libraries have added similar tools (either a special multiple buttons block or the ability to add more instances in a single button block). We should explore bring this into core, likely leveraging child blocks for the extra buttons, but in a more convenient way than forcing people to add columns first to hold each button in place.
The text was updated successfully, but these errors were encountered: