coss.com ui

Changelog

Breaking changes, migration guides, and notable updates.

October 20, 2026

Segmented Control component

@coss/segmented-control is now a component at components/ui/segmented-control.tsx instead of a styling library at lib/segmented-control.ts. It exports SegmentedControl and SegmentedControlItem. The element you pass to render still decides the behavior — a Radio Group, links, or a Toggle Group — so the semantics stay those of the primitive you choose.

The sliding indicator is built in. SegmentedControl renders it after its children, so there is nothing to add or order by hand, and before hydration the active item paints its own static pill. size is set once on SegmentedControl and inherited by its items; an item can still override it. One item recipe now covers data-checked, aria-current="page", and data-pressed, so there is no state option.

These exports were removed: segmentedControlRootClassName, segmentedControlItemVariants, segmentedControlIndicatorClassName, and SegmentedControlIndicator. The @coss/segmented-control-indicator registry item no longer exists. SegmentedControlSize, segmentedControlItemSizeClassNames, segmentedControlItemLayoutClassName, and segmentedControlIndicatorSurfaceClassName are still exported, from the component file. Tabs imports them from there, and @coss/tabs declares the component as a registry dependency.

Migration:

Install the component, then update Tabs so it no longer imports from the library:

If you maintain a local Tabs, change its import instead of overwriting it:

Replace class-based compositions. Move the root class and the indicator into SegmentedControl, and each item recipe into SegmentedControlItem, keeping behavior props on the rendered element:

Navigation follows the same shape, with the <nav> as the rendered root and the link on each item:

Extra classes from segmentedControlItemVariants({ className }) move to className on SegmentedControlItem. Once nothing imports @/lib/segmented-control or @/lib/segmented-control-indicator, delete both files.

Agent migration prompt:

October 18, 2026

Avatar group clipping and inherited sizing

AvatarGroup and AvatarGroupCount are new. Overlapping avatars are separated by masking each one with its neighbour's circle, so the gap between them is transparent rather than a coloured ring. A stack now keeps its shape on gradients, photographs and translucent panels, where a ring tinted with the page background does not.

topmost picks which end of the stack stays a whole circle — "first" by default, "last" for the conventional order.

Avatar now takes every dimension from one inherited custom property, --avatar-size (default 32px). Font size scales with it, and a group derives its overlap, gap and initials nudge from it. Set it on the avatar, the group, or any ancestor:

--avatar-overlap, --avatar-gap and --avatar-nudge tune a group and inherit the same way.

Two defaults changed: AvatarFallback uses bg-border instead of bg-muted, which is twice the contrast, and Avatar no longer paints bg-background behind its content. AvatarImage and AvatarFallback now follow the root radius through rounded-[inherit], so a rounded avatar no longer has to repeat its radius on the fallback.

Browsers without mask-composite (Chrome and Edge 111–119) fall back to a plain overlap with no gap. Nothing else degrades.

Migration:

Existing Avatar JSX requires no changes. A size-* class still resizes a single avatar, because tailwind-merge replaces the base size utility — but it leaves --avatar-size untouched, so the font size and any group geometry stay at the inherited value. Prefer the property:

Once an avatar is sized this way, a hand-tuned font size on its fallback is usually redundant:

Replacing a hand-rolled ring stack with AvatarGroup means dropping the negative spacing and the ring utilities:

If you relied on the lighter bg-muted fallback or on bg-background behind a transparent image, set those explicitly on your own instances.

Agent migration prompt:

August 19, 2026

Tabs sizing and segmented control styles

TabsList now supports a size prop with "sm", "default", and "lg" values. The size propagates to its TabsTab children, and an individual tab can override the inherited size when necessary.

The default Tabs appearance now uses the same optical item sizing as the Segmented Control pattern. The default rendered height is slightly smaller than before so the inset active indicator remains visually balanced beside a Button of the corresponding size.

Tabs now imports its size map and segmentedControlItemLayoutClassName from the @coss/segmented-control registry library. That class covers the shared icon gap, size, and opacity treatment. segmentedControlItemVariants includes it, and TabsTab uses it instead of inlining the same utilities. @coss/tabs declares this as a registry dependency, so the shadcn CLI installs it automatically with a fresh installation or CLI-managed update.

Migration:

Existing Tabs JSX requires no changes because "default" remains the default size. If you replace your local Tabs component through the CLI, review any local customizations before accepting the overwrite:

If you update tabs.tsx manually, install the shared library first and then merge the latest Tabs implementation. Copying only the new Tabs file without this dependency results in an unresolved import.

After updating, remove local height or horizontal-padding utilities from TabsList and TabsTab only where they unintentionally override the new size API. Keep intentional product-specific overrides. If you maintain a local copy of the library or Tabs, also merge segmentedControlItemLayoutClassName so icons stay optically aligned with Button.

Agent migration prompt:

July 31, 2026

Scroll Area — overscroll contain

ScrollArea no longer applies overscroll-behavior: contain by default. Use the new optional overscrollContain prop (default false) to opt in.

Nested surfaces that should not chain scroll to the page already pass it: DialogPanel, SheetPanel, DrawerPanel, ComboboxList, AutocompleteList, and SidebarContent.

Migration:

No change required for those composed parts after upgrading. For custom nested scroll areas (command menus, calendar time lists, vendored sidebar.tsx, etc.), opt in explicitly:

Agent migration prompt:

July 26, 2026

React DayPicker 10

coss ui now targets @daypicker/react@10. The legacy react-day-picker package name remains available for compatibility, but DayPicker recommends the scoped package for v10 and newer.

If you import DayPicker APIs directly, update the dependency and imports:

DayPicker v10 removes APIs deprecated in v9, including legacy navigation props, aliases, component slots, and classNames / styles keys. Applications with custom calendar wrappers should follow the DayPicker v10 migration guide.

Agent migration prompt:

June 22, 2026

Base UI 1.6.0

coss ui now targets @base-ui/react@1.6.0.

Breaking change covered in this bump: Base UI renamed the OTP namespace export from OTPFieldPreview to OTPField. coss has been updated accordingly in the OTP field implementation and docs.

If you import Base UI OTP primitives directly in your app, update:

June 11, 2026

Context Menu

@coss/context-menu is a new registry component for right-click and long-press action menus anchored to the pointer. See the Context Menu docs for installation and examples.

Install:

No migration from an existing coss primitive—opt in where you need pointer-triggered menus instead of (or alongside) Menu.

MenuLinkItem and ContextMenuLinkItem are styled wrappers for Base UI LinkItem. They match MenuItem / ContextMenuItem visually and default closeOnClick to true so the menu closes on navigation.

LinkItem renders a native <a> when you pass href. If you were already using render={<Link href="..." />} (or another router link), keep render on the link item — swap the component name only, do not drop render for href alone.

Use href only for plain anchor links with no router Link.

Migration:

Plain anchor (no router Link):

For context menus:

Existing MenuItem render={<Link … />} usage keeps working; migrate when you touch those menus.

Agent migration prompt:

May 29, 2026

Scroll Area

ScrollArea adds an optional fill prop (default false). When fill is enabled, size-full is applied to ScrollArea.Content so inner flex layouts can use the full viewport height (for example, pinning a footer with mt-auto in a sidebar).

Most scroll areas should keep the default. Opt in only when the scroll container must stretch rather than size to its children.

Migration:

No change required for existing ScrollArea usage (lists, dialogs, comboboxes, command menus). For custom sidebars or other flex columns with mt-auto footers inside a scroll area, opt in explicitly:

SidebarContent from @coss/sidebar already passes fill—update your local sidebar.tsx copy if you vendor the component.

Agent migration prompt:

Apr 17, 2026

Form

The Form component (form.tsx) no longer applies default layout classes (flex, flex-col, gap-4, w-full). It is a thin wrapper around Base UI only; pass className wherever you need a vertical field stack, width constraints, or dialog/sheet layout.

Migration:

For a typical stacked-field form, restore the previous default explicitly:

For dialogs, sheets, and drawers, keep DialogHeader (or SheetHeader, DrawerHeader) outside the form. Wrap DialogPanel and DialogFooter (or sheet/drawer equivalents) in <Form className="contents"> or a native <form className="contents">. display: contents keeps header, panel, and footer as the direct flex children of the popup’s column layout so DialogPanel scroll and height constraints work correctly.

Agent migration prompt:

Apr 14, 2026

OTP Field

The input-otp.tsx registry component has been removed in favor of otp-field.tsx (@coss/otp-field), which wraps Base UI OTP Field. See the OTP Field docs and migration guide for API details.

Migration:

Agent migration prompt:

Apr 12, 2026

Table

Table now supports an optional variant prop: "default" (the default) or "card". Omitting it keeps the same appearance as before. Use variant="card" for the card-style grid (separated rows, rounded cells, updated hover/footer treatment)—including tables inside a Frame or CardFrame as shown in the Table docs.

Migration:

No change required for existing tables. Opt in where you want the card-style table:

Agent migration prompt:

Mar 20, 2026

Toggle Group

Toggle was renamed to ToggleGroupItem in toggle-group.tsx to avoid a naming conflict with the standalone Toggle export.

Migration:

Agent migration prompt:

coss.com ui

Built by and for the team of Cal.com, Inc. — the leading commercial open source company (“coss”).