@recursica/mantine-adapter 0.55.2 → 0.55.3

package/package.json

@@ -13,7 +13,7 @@
     "url": "git+https://github.com/borderux/recursica.git",
     "directory": "packages/mantine-adapter"
   },
-  "version": "0.55.2",
+  "version": "0.55.3",
   "type": "module",
   "main": "./dist/mantine-adapter.cjs",
   "module": "./dist/mantine-adapter.js",
@@ -103,7 +103,7 @@
     "vitest": "^3.2.4"
   },
   "dependencies": {
-    "@recursica/adapter-common": "^0.28.2"
+    "@recursica/adapter-common": "^0.29.0"
   },
   "peerDependencies": {
     "@mantine/core": "^8.0.0",

package/src/components/Checkbox/CHECKBOX_IMPLEMENTATION_NOTES.md

@@ -23,3 +23,16 @@ This calculation ensures that the optical center of the `.inner` checkmark vecto
 ### Checkbox.Group Overrides
 
 To decouple `<CheckboxGroup>` away from `<Input.Wrapper>`, we explicitly extract the raw array execution mapped correctly against our identical `RecursicaFormControlWrapperProps` schema structurally!
+
+### `Checkbox.Group` `controlMaxWidth` bug (fixed 2026-08-31)
+
+`CheckboxGroup` was passing `--recursica_ui-kit_components_checkbox-item_properties_max-width`
+(400px) as its own `controlMaxWidth`. That token caps a single checkbox+its own label — it's
+already applied per-item via `.root` in `Checkbox.module.css`. Passed as the _group's_
+`controlMaxWidth`, `FormControlLayout` applies it to the whole root row (`max-width` on
+`.root`, which contains both `leftSection`/label and `rightSection`/items), so in side-by-side
+layout the group's own label got squeezed into that same 400px alongside the checkboxes. There
+is no group-level max-width token in the schema (`checkbox-group_variants_layouts_*` only
+covers gutter/margin/padding) — fixed by leaving `controlMaxWidth` `undefined`, matching
+`SwitchGroup`'s existing pattern. Same bug existed in `RadioGroup` (`radio-button-item_
+properties_max-width`), fixed the same way.

package/src/components/Checkbox/CheckboxGroup.tsx

@@ -89,7 +89,11 @@ export const CheckboxGroup = forwardRef<HTMLDivElement, CheckboxGroupProps>(
       <WithReadOnlyWrapper
         className={className}
         style={style as React.CSSProperties}
-        controlMaxWidth="var(--recursica_ui-kit_components_checkbox-item_properties_max-width)"
+        // Not the group's own row width: this token caps a single checkbox+its own label
+        // (applied per-item in Checkbox.module.css's `.root`). The group has no max-width token
+        // of its own in the schema, so this must stay undefined or FormControlLayout caps the
+        // whole label+items row (including the group's own label) at 400px in side-by-side layout.
+        controlMaxWidth={undefined}
         controlMinWidth={undefined}
         overStyled={overStyled as true}
         labelElement="div" // Strictly override. ARIA grouping prohibits interactive checkboxes nested natively inside <label>.

package/src/components/Chip/Chip.stories.tsx

@@ -124,3 +124,31 @@ export const WithLeadingIconSelected: Story = {
   },
   render: (args: ChipStoryProps) => <Chip {...args} onChange={() => {}} />,
 };
+
+// A label long enough to exceed the chip's own max-width token — should stay a single line and
+// truncate with an ellipsis, never wrap, even with both a leading icon and a dismiss button
+// competing for space.
+export const MaxWidthEllipsis: Story = {
+  args: {
+    children:
+      "A very long chip label that exceeds the maximum width and should truncate with an ellipsis",
+    checked: false,
+    icon: (
+      <svg
+        xmlns="http://www.w3.org/2000/svg"
+        viewBox="0 0 24 24"
+        fill="none"
+        stroke="currentColor"
+        strokeWidth="2"
+        strokeLinecap="round"
+        strokeLinejoin="round"
+      >
+        <circle cx="12" cy="12" r="10"></circle>
+        <path d="M12 8v4"></path>
+        <path d="M12 16h.01"></path>
+      </svg>
+    ),
+    onDelete: () => console.log("Removal Action Triggered"),
+  },
+  render: (args: ChipStoryProps) => <Chip {...args} />,
+};

package/src/components/Radio/RADIO_IMPLEMENTATION_NOTES.md

@@ -0,0 +1,12 @@
+# Radio Implementation Notes
+
+### `Radio.Group` `controlMaxWidth` bug (fixed 2026-08-31)
+
+`RadioGroup` was passing `--recursica_ui-kit_components_radio-button-item_properties_max-width`
+(400px) as its own `controlMaxWidth`. That token caps a single radio+its own label — it's
+already applied per-item via `.root` in `Radio.module.css`. Passed as the _group's_
+`controlMaxWidth`, `FormControlLayout` applies it to the whole root row, so in side-by-side
+layout the group's own label got squeezed into that same 400px alongside the radios. There is
+no group-level max-width token in the schema — fixed by leaving `controlMaxWidth` `undefined`,
+matching `SwitchGroup`'s existing pattern. Same bug existed in `CheckboxGroup`, fixed the same
+way — see `Checkbox/CHECKBOX_IMPLEMENTATION_NOTES.md`.

package/src/components/Radio/RadioGroup.tsx

@@ -78,7 +78,11 @@ export const RadioGroup = forwardRef<HTMLDivElement, RadioGroupProps>(
       <WithReadOnlyWrapper
         className={className}
         style={style as React.CSSProperties}
-        controlMaxWidth="var(--recursica_ui-kit_components_radio-button-item_properties_max-width)"
+        // Not the group's own row width: this token caps a single radio+its own label (applied
+        // per-item in Radio.module.css's `.root`). The group has no max-width token of its own
+        // in the schema, so this must stay undefined or FormControlLayout caps the whole
+        // label+items row (including the group's own label) at 400px in side-by-side layout.
+        controlMaxWidth={undefined}
         controlMinWidth={undefined}
         overStyled={overStyled as true}
         labelElement="div" // Strictly override. ARIA grouping prohibits interactive radios nested natively inside <label>.