Problem

The Button block currently behaves as a container for a single item. When more than one Button is added inside it, percentage-based widths fail — they are calculated against the entire viewport or parent container instead of being distributed among sibling buttons. There is no way to make two or more buttons grow proportionally within the same Button block.

Proposed Solution

Allow the Button block to behave as a flex row container when it holds multiple Button items. And introduce per-button width controls modeled after the existing Row block UI. Under a Width setting in the Button inspector panel, each individual Button would offer three options:

• Fit: shrinks to the size of its label
• Grow: expands to fill available space in the row
• Fixed: accepts a specific value (px, %, rem)

Expected Behavior

• A single Button continues to work exactly as it does today
• When two or more Buttons are present, the container switches to row layout
• Each Button exposes the Fit / Grow / Fixed width control in its own inspector panel
• The controls and labels mirror the existing Row block experience for consistency

Why This Matters

Side-by-side button layouts — primary/secondary CTAs, yes/no choices, multi-step navigation — are among the most common design patterns on the web. The Fit / Grow / Fixed model already exists in the editor and is intuitive for designers. Bringing it to the Button block eliminates the need for workarounds and makes the experience native, clean, and consistent.