@anchrd/intel-ui 0.45.0 → 0.46.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anchrd/intel-ui",
-  "version": "0.45.0",
+  "version": "0.46.0",
   "type": "module",
   "license": "UNLICENSED",
   "repository": {

package/src/board/board-assignee/board-assignee.ts

@@ -25,3 +25,24 @@ export function useAssigneeLabel(id: string | null): string {
   // replacement for the rule underneath it.
   return own ?? resolved ?? i18n.t("node.someUser");
 }
+
+/**
+ * The three tones the access summary already uses for its circles, so an assignee looks like the
+ * same kind of thing as a person on the share screen (#724).
+ *
+ * ⚠️ **Chosen by the ID, not by a position.** The access summary can count places in a row; a card
+ * stands alone, and there is no row to count in. Hashing the id means the same person keeps the same
+ * colour on every card and every board, which is the only property that makes a colour worth having
+ * here — a colour that moves is noise.
+ */
+const PERSON_TONES = [
+  "bg-muted text-muted-foreground",
+  "bg-accent text-accent-foreground",
+  "bg-secondary text-secondary-foreground",
+] as const;
+
+export function personTone(id: string): string {
+  let sum = 0;
+  for (const character of id) sum = (sum + character.charCodeAt(0)) % 4096;
+  return PERSON_TONES[sum % PERSON_TONES.length] ?? PERSON_TONES[0];
+}

package/src/board/board-assignee/board-assignee.tsx

@@ -1,10 +1,12 @@
+import { UserRound } from "lucide-react";
 import { AssigneePicker } from "@/board/board-assignee/board-assignee-picker.tsx";
 import { useI18n } from "@/i18n/i18n-context.tsx";
+import { cn } from "@/lib/utils";
 import { initials } from "@/user-name/user-name.ts";
-import { useAssigneeLabel } from "./board-assignee.ts";
+import { personTone, useAssigneeLabel } from "./board-assignee.ts";
 
 /**
- * The circle for whoever a card is for, and the way to take the assignment off.
+ * The circle for whoever a card is for, and the way to give it to somebody else.
  *
  * ⚠️ **One truth for two surfaces.** The opened card and the table both draw it; written twice they
  * would drift, and the drift would be an accessibility bug on exactly one of them.
@@ -12,8 +14,10 @@ import { useAssigneeLabel } from "./board-assignee.ts";
  * ⚠️ **One person, not a group.** Jack's decision 2026-08-20: the STYLE is borrowed from the access
  * summary, the field stays `assigneeId`. A row of circles would imply a second data model.
  *
- * ⚠️ **Only ever drawn for somebody.** "Nobody yet" as a chip is a placeholder for an absence, and
- * an absence needs no place on screen (#692).
+ * ⚠️ **Drawn even for nobody, since #724** — and that reverses #692 on purpose rather than by
+ * accident. A text chip saying "nobody yet" was a placeholder for an absence and earned no room. An
+ * empty circle is not that: it is the one control on the row that says the card COULD be given to
+ * somebody, and the card nobody owns is exactly the one that needs it.
  *
  * ⚠️ **The circle OPENS the picker; it no longer clears on click** (#723). A control that
  * removes an assignment on the same click somebody uses to change one is a control that
@@ -29,7 +33,12 @@ export function AssigneeChip({
   boardId,
   onPick,
 }: {
-  id: string;
+  /**
+   * ⚠️ `null` DRAWS, it does not skip (#724). An empty circle with a person in it is the one place
+   * on the row that says "this could be given to somebody" — and without it there is nothing to
+   * press on a card nobody owns, which is exactly the card that needs an owner.
+   */
+  id: string | null;
   boardId: string;
   onPick(assigneeId: string | null): void;
 }) {
@@ -39,7 +48,11 @@ export function AssigneeChip({
     <AssigneePicker boardId={boardId} current={id} onPick={onPick}>
       <button
         type="button"
-        aria-label={i18n.t("board.changeAssignee", { name: label })}
+        aria-label={
+          id === null
+            ? i18n.t("board.assignSomebody")
+            : i18n.t("board.changeAssignee", { name: label })
+        }
         title={label}
         className="shrink-0 rounded-full outline-none focus-visible:ring-2 focus-visible:ring-ring"
       >
@@ -49,9 +62,12 @@ export function AssigneeChip({
           // label back would not add a second announcement, it would add none, while making the code
           // look as though the name were covered here rather than on the button.
           aria-hidden="true"
-          className="flex size-7 items-center justify-center rounded-full bg-accent text-xs font-medium text-accent-foreground ring-2 ring-background"
+          className={cn(
+            "flex size-7 items-center justify-center rounded-full text-xs font-medium ring-2 ring-background",
+            id === null ? "border border-dashed text-muted-foreground" : personTone(id),
+          )}
         >
-          {initials(label)}
+          {id === null ? <UserRound aria-hidden="true" className="size-4" /> : initials(label)}
         </span>
       </button>
     </AssigneePicker>

package/src/board/board-chip/board-chip.tsx

@@ -1,3 +1,4 @@
+import { cn } from "@/lib/utils";
 /**
  * A value on a card, and the way to take it off again.
  *
@@ -13,17 +14,31 @@ export function BoardChip({
   label,
   action,
   onClick,
+  tone = "outline",
 }: {
   label: string;
   action: string;
   onClick(): void;
+  /**
+   * ⚠️ **`inverted` is for labels and nothing else** (#724). Status, dates and the assignee say what
+   * a card IS; a label is what somebody chose to call it, and the row needs to tell the two apart at
+   * a glance. Filling every chip would take that difference away again.
+   */
+  tone?: "outline" | "inverted";
 }) {
   return (
     <button
       type="button"
       aria-label={`${label}, ${action}`}
       onClick={onClick}
-      className="shrink-0 rounded-full border px-2.5 py-0.5 text-xs tabular-nums outline-none hover:bg-muted focus-visible:ring-2 focus-visible:ring-ring"
+      className={cn(
+        "flex shrink-0 items-center gap-1.5 rounded-full px-2.5 py-0.5 text-xs tabular-nums outline-none focus-visible:ring-2 focus-visible:ring-ring",
+        tone === "outline" && "border hover:bg-muted",
+        // ⚠️ `foreground`/`background`, not literal black and white. The two swap with the theme on
+        // their own, so the label stays inverted in dark mode instead of turning into a black chip
+        // on a black ground.
+        tone === "inverted" && "bg-foreground text-background hover:bg-foreground/85",
+      )}
     >
       {label}
     </button>

package/src/board/board-crumbs/board-crumbs.tsx

@@ -31,14 +31,17 @@ export function BoardCrumbs({
   const rest = shown.slice(1);
 
   return (
-    <nav aria-label={i18n.t("board.crumbs")} className="flex min-w-0 items-center gap-1.5 text-sm">
+    <nav
+      aria-label={i18n.t("board.crumbs")}
+      className="flex min-w-0 items-center gap-1.5 text-lg font-semibold"
+    >
       <button
         type="button"
         aria-label={i18n.t("board.backTo", { board: board?.title ?? "" })}
         onClick={() => onOpen(null)}
         className="-ml-1 rounded-md p-0.5 text-muted-foreground outline-none hover:text-foreground focus-visible:ring-2 focus-visible:ring-ring"
       >
-        <ChevronLeft aria-hidden="true" className="size-4" />
+        <ChevronLeft aria-hidden="true" className="size-5" />
       </button>
 
       <Step crumb={board} onOpen={onOpen} />

package/src/board/board-dates/board-dates.ts

@@ -0,0 +1,40 @@
+/**
+ * The one place a card's two dates become the one thing a reader sees (#724).
+ *
+ * ⚠️ **Pure, and separate from the chip that draws it.** The rules here — which of the four
+ * combinations produces which text — are the part worth holding in a test without a DOM, and the
+ * part a second surface would otherwise re-derive slightly differently.
+ */
+
+/**
+ * `TT.MM.JJJJ`, from the ISO timestamp the contract carries.
+ *
+ * ⚠️ Built from the date PART of the string, never from a `Date`. `new Date("2026-08-15T00:00:00Z")`
+ * is the 14th in every timezone west of London, and a card would show the day before the one
+ * somebody picked. The stored value is a calendar day; it is read as one.
+ */
+export function germanDate(iso: string): string {
+  const [year, month, day] = iso.slice(0, 10).split("-");
+  return `${day}.${month}.${year}`;
+}
+
+/** What the `<input type="date">` in the popover needs: the same day, the other way round. */
+export function isoDay(iso: string): string {
+  return iso.slice(0, 10);
+}
+
+/**
+ * The label of the single date chip, or `null` when there is nothing to say.
+ *
+ * ⚠️ **A range only when there IS one.** With one date set the chip carries that date alone: a
+ * range with an empty half ("15.08.2026 - ") reads as a value somebody forgot to finish, and a
+ * placeholder for the missing end is a placeholder for an absence (#692).
+ */
+export function dateLabel(startDate: string | null, dueDate: string | null): string | null {
+  if (startDate !== null && dueDate !== null) {
+    return `${germanDate(startDate)} - ${germanDate(dueDate)}`;
+  }
+  if (startDate !== null) return germanDate(startDate);
+  if (dueDate !== null) return germanDate(dueDate);
+  return null;
+}

package/src/board/board-dates/board-dates.tsx

@@ -0,0 +1,105 @@
+import { CalendarDays } from "lucide-react";
+import {
+  DropdownMenu,
+  DropdownMenuContent,
+  DropdownMenuTrigger,
+} from "@/components/ui/dropdown-menu.tsx";
+import { useI18n } from "@/i18n/i18n-context.tsx";
+import { dateLabel, isoDay } from "./board-dates.ts";
+
+/**
+ * When a card runs, as one chip (#724).
+ *
+ * ⚠️ **One chip, not two.** It used to be `from …` and `due …` side by side, and that was two facts
+ * where a reader sees one: a card runs from a day to a day. The two are still edited and removed
+ * separately, but inside, where the popover can say which half it is changing.
+ *
+ * ⚠️ **The chip is the trigger.** A menu with no anchor never appears — that is `#723`, and it cost
+ * a whole release. `DropdownMenuContent` without a `DropdownMenuTrigger` in the same `DropdownMenu`
+ * is a finding in this repository.
+ */
+export function DatesChip({
+  startDate,
+  dueDate,
+  write,
+}: {
+  startDate: string | null;
+  dueDate: string | null;
+  write(input: { startDate?: string | null; dueDate?: string | null }): void;
+}) {
+  const i18n = useI18n();
+  const label = dateLabel(startDate, dueDate);
+  if (label === null) return null;
+
+  // ⚠️ Midnight UTC, the same shape the plus menu writes. A card's dates are calendar days here, and
+  // a second format would make two cards written by two paths sort against each other.
+  const asStored = (day: string) => (day === "" ? null : `${day}T00:00:00.000Z`);
+
+  return (
+    <DropdownMenu>
+      <DropdownMenuTrigger
+        aria-label={`${label}, ${i18n.t("board.dates.edit")}`}
+        className="flex shrink-0 items-center gap-1.5 rounded-full border px-2.5 py-0.5 text-xs tabular-nums outline-none hover:bg-muted focus-visible:ring-2 focus-visible:ring-ring"
+      >
+        <CalendarDays aria-hidden="true" className="size-3.5" />
+        {label}
+      </DropdownMenuTrigger>
+      <DropdownMenuContent align="start" className="w-60 p-2">
+        <div className="flex flex-col gap-2">
+          <Field
+            label={i18n.t("board.add.start")}
+            value={startDate}
+            clear={i18n.t("board.clearStart")}
+            onChange={(day) => write({ startDate: asStored(day) })}
+          />
+          <Field
+            label={i18n.t("board.add.due")}
+            value={dueDate}
+            clear={i18n.t("board.clearDue")}
+            onChange={(day) => write({ dueDate: asStored(day) })}
+          />
+        </div>
+      </DropdownMenuContent>
+    </DropdownMenu>
+  );
+}
+
+/**
+ * One half of the range.
+ *
+ * ⚠️ **The remove button only exists while there is something to remove.** A permanently visible
+ * one is a control that does nothing on most cards, and a reader learns to ignore it.
+ */
+function Field({
+  label,
+  value,
+  clear,
+  onChange,
+}: {
+  label: string;
+  value: string | null;
+  clear: string;
+  onChange(day: string): void;
+}) {
+  return (
+    <label className="flex items-center gap-2 text-xs">
+      <span className="w-14 shrink-0 text-muted-foreground">{label}</span>
+      <input
+        type="date"
+        value={value === null ? "" : isoDay(value)}
+        onChange={(event) => onChange(event.target.value)}
+        className="min-w-0 flex-1 rounded-md border bg-background px-2 py-1 tabular-nums outline-none focus-visible:ring-2 focus-visible:ring-ring"
+      />
+      {value === null ? null : (
+        <button
+          type="button"
+          aria-label={`${label}, ${clear}`}
+          onClick={() => onChange("")}
+          className="shrink-0 rounded-md px-1 text-muted-foreground outline-none hover:bg-muted hover:text-foreground focus-visible:ring-2 focus-visible:ring-ring"
+        >
+          ×
+        </button>
+      )}
+    </label>
+  );
+}

package/src/board/board-task/board-task.ts

@@ -96,10 +96,3 @@ export function linksOf(task: BoardTask, columns: ColumnWithCards[]): TaskLink[]
       (a.title ?? "").localeCompare(b.title ?? ""),
   );
 }
-
-/** How far the subtasks have got — `null` when there are none, so the view draws nothing. */
-export function progressOf(links: TaskLink[]): { done: number; total: number } | null {
-  const subtasks = links.filter((link) => link.kind === "subtask");
-  if (subtasks.length === 0) return null;
-  return { done: subtasks.filter((link) => link.done).length, total: subtasks.length };
-}

package/src/board/board-task/board-task.tsx

@@ -5,6 +5,7 @@ import { AssigneeChip } from "@/board/board-assignee/board-assignee.tsx";
 import { AssigneePicker } from "@/board/board-assignee/board-assignee-picker.tsx";
 import { BoardChip } from "@/board/board-chip/board-chip.tsx";
 import type { BoardHandle } from "@/board/board-data/board-data.types.ts";
+import { DatesChip } from "@/board/board-dates/board-dates.tsx";
 import { StatusChip } from "@/board/board-status/board-status.tsx";
 import {
   DropdownMenu,
@@ -13,7 +14,7 @@ import {
   DropdownMenuTrigger,
 } from "@/components/ui/dropdown-menu.tsx";
 import { useI18n } from "@/i18n/i18n-context.tsx";
-import { type LinkKind, linksOf, progressOf, type TaskLink } from "./board-task.ts";
+import { type LinkKind, linksOf, type TaskLink } from "./board-task.ts";
 
 const linkIcons: Record<LinkKind, typeof Lock> = {
   subtask: Square,
@@ -66,7 +67,6 @@ export function BoardTaskDocument({
   const i18n = useI18n();
 
   const links = linksOf(task, board.columns);
-  const progress = progressOf(links);
   const columns = board.columns.filter((entry) => entry.unknown !== true).map((e) => e.column);
   const column = columns.find((entry) => entry.id === task.status);
 
@@ -87,7 +87,11 @@ export function BoardTaskDocument({
 
   return (
     <div
-      className="flex min-h-0 flex-1 flex-col gap-4 overflow-auto p-6"
+      /* ⚠️ `pt-0`, and the 16px above the chips is the TITLE ROW's own `py-4` (#724). Adding padding
+         here as well would stack two gaps into 40px, which is what it was: the chips looked like a
+         section of their own instead of the second line of one head. `gap-6` below sets the 24px
+         that separates the head from the link list, which IS a section of its own. */
+      className="flex min-h-0 flex-1 flex-col gap-6 overflow-auto px-6 pt-0 pb-6"
       aria-busy={board.isWriting}
     >
       {/* ⚠️ No heading and no way back HERE. Both live in the title row above since #692: the path
@@ -103,43 +107,32 @@ export function BoardTaskDocument({
           write={write}
         />
 
-        {/* ⚠️ Two chips when both dates are set, not a range. A range reads as one fact; these
-            are two, and each is removed on its own. */}
-        {task.startDate === null ? null : (
-          <BoardChip
-            label={i18n.t("board.fromDate", { date: task.startDate.slice(0, 10) })}
-            action={i18n.t("board.clearStart")}
-            onClick={() => write({ startDate: null })}
-          />
-        )}
-        {task.dueDate === null ? null : (
-          <BoardChip
-            label={i18n.t("board.untilDate", { date: task.dueDate.slice(0, 10) })}
-            action={i18n.t("board.clearDue")}
-            onClick={() => write({ dueDate: null })}
-          />
-        )}
+        {/* ⚠️ ONE chip, since #724. It was two, `from …` and `due …` — two facts where a reader
+            sees one: a card runs from a day to a day. Each half is still edited and removed on its
+            own, but inside the popover, where the control can say which half it means. */}
+        <DatesChip startDate={task.startDate} dueDate={task.dueDate} write={write} />
 
         {task.labels.map((entry) => (
           <BoardChip
             key={entry}
             label={entry}
+            tone="inverted"
             action={i18n.t("board.removeLabel")}
             onClick={() => write({ labels: task.labels.filter((keep) => keep !== entry) })}
           />
         ))}
 
-        {/* ⚠️ **Last, always.** It is the only round element in the row; standing between the chips
-            it breaks the line, and a row without one simply ends earlier. */}
-        {task.assigneeId === null ? null : (
-          <AssigneeChip
-            id={task.assigneeId}
-            boardId={board.boardId}
-            onPick={(assigneeId) => write({ assigneeId })}
-          />
-        )}
-
         <Adder task={task} board={board} write={write} />
+
+        {/* ⚠️ **Last, always, and after the plus** (#724). It is the only round element in the row;
+            standing between the chips it breaks the line. And it is drawn even when nobody has the
+            card: an empty circle is the one control on a row that says the card COULD be given to
+            somebody, which is precisely what an unowned card needs. */}
+        <AssigneeChip
+          id={task.assigneeId}
+          boardId={board.boardId}
+          onPick={(assigneeId) => write({ assigneeId })}
+        />
       </div>
 
       {/* ⚠️ ONE list, not three blocks: the icon carries the kind. And it exists only when there is
@@ -147,14 +140,11 @@ export function BoardTaskDocument({
           is missing; nothing at all tells them there is nothing, which is the truth (#692). */}
       {links.length === 0 ? null : (
         <section aria-label={i18n.t("board.links")} className="flex flex-col gap-1">
-          <h2 className="flex items-center gap-2 text-sm font-medium">
-            {i18n.t("board.links")}
-            {progress === null ? null : (
-              <span className="text-xs text-muted-foreground tabular-nums">
-                {i18n.t("board.progress", { done: progress.done, total: progress.total })}
-              </span>
-            )}
-          </h2>
+          {/* ⚠️ Secondary, and the counter is gone (#724). The heading is a label for the list
+              under it, not a section title competing with the card's name; and "0 of 2 done" was a
+              number nobody acts on — the rows themselves say which are done, and they say it
+              without arithmetic. */}
+          <h2 className="text-xs text-muted-foreground">{i18n.t("board.links")}</h2>
           <ul className="flex flex-col">
             {links.map((link) => (
               <LinkRow key={`${link.kind}:${link.id}`} link={link} onOpen={onOpen} />
@@ -258,11 +248,14 @@ function Adder({
   return (
     <>
       <DropdownMenu>
+        {/* ⚠️ No border, square, and the icon at full strength (#724). A bordered pill here read
+            as one more chip, so the row looked like it carried a value called "+". Without the
+            border it is what it is: a control, quiet until the pointer is on it. */}
         <DropdownMenuTrigger
           aria-label={i18n.t("board.add")}
-          className="rounded-full border px-2 py-0.5 text-xs outline-none hover:bg-muted focus-visible:ring-2 focus-visible:ring-ring"
+          className="flex size-6 shrink-0 items-center justify-center rounded-md text-foreground outline-none hover:bg-muted focus-visible:ring-2 focus-visible:ring-ring"
         >
-          <Plus aria-hidden="true" className="size-3" />
+          <Plus aria-hidden="true" className="size-4" />
         </DropdownMenuTrigger>
         <DropdownMenuContent align="start">
           {addable.map((entry) => (

package/src/i18n/de.json

@@ -84,6 +84,7 @@
   "board.addCardIn": "Eine Aufgabe zu {column} hinzufügen",
   "board.addLabel": "Label hinzufügen",
   "board.addLink": "Verlinkung",
+  "board.assignSomebody": "Jemandem zuweisen",
   "board.assignee.clear": "Zuständigkeit entfernen",
   "board.assignee.keepTyping": "Mindestens zwei Zeichen tippen",
   "board.assignee.nobody": "Niemand mit Zugriff auf dieses Board passt dazu",
@@ -110,6 +111,7 @@
   "board.createFailed": "Die Aufgabe konnte nicht angelegt werden.",
   "board.crumbs": "Wo diese Karte sitzt",
   "board.crumbsFolded": "Die Ebenen dazwischen zeigen",
+  "board.dates.edit": "Zeitraum bearbeiten",
   "board.drag.lifted": "{card} aufgenommen",
   "board.drag.moved": "{card} nach {column} verschoben",
   "board.drag.putBack": "{card} zurückgelegt",
@@ -127,7 +129,6 @@
   "board.link.subtask": "Unteraufgabe",
   "board.links": "Verlinkt",
   "board.moveTo": "in eine andere Spalte verschieben",
-  "board.progress": "{done} von {total} erledigt",
   "board.removeLabel": "dieses Label entfernen",
   "board.settings.addColumn": "+ Spalte",
   "board.settings.columnName": "Name der Spalte {column}",

package/src/i18n/en.json

@@ -84,6 +84,7 @@
   "board.addCardIn": "Add a task to {column}",
   "board.addLabel": "Add a label",
   "board.addLink": "Link",
+  "board.assignSomebody": "Assign to somebody",
   "board.assignee.clear": "Remove the assignee",
   "board.assignee.keepTyping": "Type at least two characters",
   "board.assignee.nobody": "Nobody with access to this board matches",
@@ -110,6 +111,7 @@
   "board.createFailed": "The task could not be created.",
   "board.crumbs": "Where this card sits",
   "board.crumbsFolded": "Show the levels in between",
+  "board.dates.edit": "Edit the dates",
   "board.drag.lifted": "{card} picked up",
   "board.drag.moved": "{card} moved to {column}",
   "board.drag.putBack": "{card} put back",
@@ -127,7 +129,6 @@
   "board.link.subtask": "Subtask",
   "board.links": "Linked",
   "board.moveTo": "move it to another column",
-  "board.progress": "{done} of {total} done",
   "board.removeLabel": "remove this label",
   "board.settings.addColumn": "+ Column",
   "board.settings.columnName": "Name of the column {column}",

package/src/i18n/es.json

@@ -84,6 +84,7 @@
   "board.addCardIn": "Añadir una tarea a {column}",
   "board.addLabel": "Añadir etiqueta",
   "board.addLink": "Vínculo",
+  "board.assignSomebody": "Asignar a alguien",
   "board.assignee.clear": "Quitar el responsable",
   "board.assignee.keepTyping": "Escribe al menos dos caracteres",
   "board.assignee.nobody": "Nadie con acceso a este tablero coincide",
@@ -110,6 +111,7 @@
   "board.createFailed": "No se pudo crear la tarea.",
   "board.crumbs": "Dónde está esta tarjeta",
   "board.crumbsFolded": "Mostrar los niveles intermedios",
+  "board.dates.edit": "Editar las fechas",
   "board.drag.lifted": "{card} recogida",
   "board.drag.moved": "{card} movida a {column}",
   "board.drag.putBack": "{card} devuelta",
@@ -127,7 +129,6 @@
   "board.link.subtask": "Subtarea",
   "board.links": "Vinculado",
   "board.moveTo": "moverla a otra columna",
-  "board.progress": "{done} de {total} hechas",
   "board.removeLabel": "quitar esta etiqueta",
   "board.settings.addColumn": "+ Columna",
   "board.settings.columnName": "Nombre de la columna {column}",

package/src/title-row/title-row.tsx

@@ -121,7 +121,12 @@ export function TitleRow({
     <div
       data-scrolled={scroll?.scrolled || undefined}
       className={cn(
-        "relative z-10 flex shrink-0 items-start justify-between gap-5 px-6 py-4 transition-shadow",
+        "relative z-10 flex shrink-0 justify-between gap-5 px-6 py-4 transition-shadow",
+        // ⚠️ Two alignments for two shapes (#724). A document's name can carry a description under
+        // it, so its block starts at the top and the menu lines up with the FIRST line. A path is
+        // always one line, and starting it at the top leaves it sitting a hair above the icons it
+        // shares the row with. Centred, the two read as one line, which is what they are.
+        crumbs === undefined ? "items-start" : "items-center",
         (separated || scroll?.scrolled) && "shadow-[inset_0_-1px_0_var(--border)]",
       )}
     >