Group

Panel surface background of the group container.

Panel chrome — opt into a bordered/padded/filled container drawn AROUND the joined children. By default Group is chrome-less (the outline is the children's own borders).

Panel interactive border treatment applied to the opt-in container frame.

Panel emphasis (primary / secondary / tertiary) for the opt-in container frame.

Corner radius of the framed container. By default the radius is owned by the `size` variant (so joined children nest concentrically). Pass an explicit `radius` to override that size-derived default — useful when the Group frames a chrome'd container (e.g. a segmented nav) that must match a sibling's radius rather than its own size scale.

Opt out of the Panel's reserved 1px border footprint. The default keeps the reserved space so toggling border variants never shifts layout; set `false` on a chrome-less group that must not add 1px around the joined set (e.g. a structural join-group nested inside a parent that already owns the frame).

Panel shadow elevation applied to the opt-in container frame.

Border radius matching the size of the inner controls (`controls` variant).

Semantic color palette for the group, inherited by children and any opt-in frame.

Render the container frame with a translucent (frosted) surface.

Stretch the group to fill its container's width.

Lay children out in a row or a column.

Panel padding — inner spacing of the group container.

Layout mode. `controls` (default) joins children into one connected unit using their OWN borders — it flattens the corners where they meet and overlaps adjacent borders into a single seam (no group frame, no double border). `stack` renders children as an avatar face pile with overlap and leftmost-on-top cascade.

Enable Panel interactive (hover/press) affordances on the container frame.

Default content.

Additional class name(s) merged onto the group's root element.

Bound reference to the root element (`bind:this`).

Per-slot style and attribute override bag for the group's root element.

Astro / vanilla: serialize the props into `data-group-config` so the client runtime hydrates this instance and `getPindoba(el, "group")` can `update()` it. Frameworks with their own reactivity don't need it.