@recursica/mantine-adapter 0.50.6 → 0.51.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -13,7 +13,7 @@
13
13
  "url": "git+https://github.com/borderux/recursica.git",
14
14
  "directory": "packages/mantine-adapter"
15
15
  },
16
- "version": "0.50.6",
16
+ "version": "0.51.0",
17
17
  "type": "module",
18
18
  "main": "./dist/mantine-adapter.cjs",
19
19
  "module": "./dist/mantine-adapter.js",
@@ -60,3 +60,13 @@ and silently override the `leftIcon`-derived element (spread order would let it
60
60
  to set that slot is through `leftIcon`. Mantine's separate, per-control `chevron` override
61
61
  is _not_ omitted — nothing here computes it, so it still passes through safely if a caller
62
62
  wants to override the cascaded container-level chevron for a single item.
63
+
64
+ ---
65
+
66
+ ## `.label` descender clipping (Matt Massey, 2026-08-28)
67
+
68
+ `.label` used plain `overflow: hidden` to make `text-overflow: ellipsis` work, which also clips
69
+ descenders (e.g. the "g" in a long title) whenever `text_line-height` is tighter than the font's
70
+ natural ascent+descent. Switched to `overflow: clip; overflow-clip-margin: 0.35em;` — same
71
+ truncation, but ink can bleed slightly past the line box before it's actually clipped. Project-wide
72
+ fix; see Chip's `CHIP_IMPLEMENTATION_NOTES.md` for the original discovery.
@@ -211,7 +211,11 @@
211
211
  text-align: left;
212
212
  color: inherit;
213
213
  padding: 0; /* Clear Mantine inner padding */
214
- overflow: hidden;
214
+ overflow: clip; /* HARDCODE: `hidden` clipped descenders (e.g. "g") whenever the text_line-height
215
+ token is tighter than the font's natural ascent+descent; `overflow-clip-margin` gives ink a
216
+ small bleed allowance while still clipping genuinely overflowing text — same fix project-wide,
217
+ see Chip/FileInput's IMPLEMENTATION_NOTES.md for the original discovery. */
218
+ overflow-clip-margin: 0.35em;
215
219
  white-space: nowrap;
216
220
  text-overflow: ellipsis;
217
221
  }
@@ -34,4 +34,9 @@ rendering with our own value comparison.
34
34
 
35
35
  ## `wrapItemText`
36
36
 
37
- `label`/`supportingText` default to single-line truncation with an ellipsis (`.optionText > *` — `overflow: hidden; text-overflow: ellipsis; white-space: nowrap`). Passing `wrapItemText` adds `.optionTextWrap` alongside `.optionText`, which re-enables wrapping (`white-space: normal; overflow-wrap: anywhere`) for both children — same later-cascade-wins mechanism (`.optionTextWrap > *` declared after `.optionText > *`, equal specificity) as the rest of this file's overrides. `renderRichOption`/`renderRichOptionContent` (shared util, both adapters) take `wrapItemText` as a third parameter and combine the two class names when it's true.
37
+ `label`/`supportingText` default to single-line truncation with an ellipsis (`.optionText > *` — `overflow: clip; overflow-clip-margin: 0.35em; text-overflow: ellipsis; white-space: nowrap`). Passing `wrapItemText` adds `.optionTextWrap` alongside `.optionText`, which re-enables wrapping (`white-space: normal; overflow-wrap: anywhere`) for both children — same later-cascade-wins mechanism (`.optionTextWrap > *` declared after `.optionText > *`, equal specificity) as the rest of this file's overrides. `renderRichOption`/`renderRichOptionContent` (shared util, both adapters) take `wrapItemText` as a third parameter and combine the two class names when it's true.
38
+
39
+ `.optionText > *` used plain `overflow: hidden` until 2026-08-28 (Matt Massey) — it clipped
40
+ descenders (e.g. "g") whenever `text_line-height` is tighter than the font's natural
41
+ ascent+descent. `overflow-clip-margin` gives ink a small bleed allowance while still clipping
42
+ genuinely overflowing text; same project-wide fix as Chip's `CHIP_IMPLEMENTATION_NOTES.md`.
@@ -304,7 +304,10 @@
304
304
 
305
305
  /* Default: label/supportingText each truncate to a single line with an ellipsis. */
306
306
  .optionText > * {
307
- overflow: hidden;
307
+ overflow: clip; /* HARDCODE: `hidden` clips descenders (e.g. "g") when text_line-height is
308
+ tighter than the font's natural ascent+descent; overflow-clip-margin gives ink a small bleed
309
+ allowance while still clipping genuinely overflowing text (see Chip's IMPLEMENTATION_NOTES.md). */
310
+ overflow-clip-margin: 0.35em;
308
311
  text-overflow: ellipsis;
309
312
  white-space: nowrap;
310
313
  }
@@ -72,7 +72,10 @@
72
72
  .labelText {
73
73
  display: block;
74
74
  min-width: 0;
75
- overflow: hidden;
75
+ overflow: clip; /* HARDCODE: `hidden` clips descenders (e.g. "g") when text_line-height is
76
+ tighter than the font's natural ascent+descent; overflow-clip-margin gives ink a small bleed
77
+ allowance while still clipping genuinely overflowing text (see Chip's IMPLEMENTATION_NOTES.md). */
78
+ overflow-clip-margin: 0.35em;
76
79
  text-overflow: ellipsis;
77
80
  white-space: nowrap;
78
81
  font-size: inherit;
@@ -69,3 +69,15 @@ Mantine's `.mantine-Button-label` flex centering breaks primitive truncation log
69
69
  **Bug:** with `overStyled` and a custom `className` (surfaced by Tree embedding a `Button` for its expand chevron — see `Tree/IMPLEMENTATION_NOTES.md`), `finalClass` (`` `${styles.root} ${classNameProp}` ``) was set explicitly on `<MantineButton>`, but `{...sanitizedProps}` was spread _after_ it — and `sanitizedProps` still contained the original, unmodified `className` key, since it had only been _read_, never deleted. The later spread would silently overwrite `finalClass` with just the caller's own class. Same bug class as `Dropdown.tsx`/`BareDropdown.tsx` had.
70
70
 
71
71
  **Why it wasn't visible here:** `classNames={{root: mergedClassNames.root, ...}}` is a _separate_ Mantine prop from the plain `className` string, unaffected by the overwrite, and `mergedClassNames.root` always includes `styles.root` independently — so the root element kept its Recursica styling regardless of the bug. mui-adapter's equivalent `Button.tsx` has no such secondary path (`@mui/material` only has a plain `className`), so the identical mistake there was fully visible (chevron rendered in MUI's own default color). Fixed in both regardless, since this is a real latent bug independent of whether it happens to be masked today.
72
+
73
+ ---
74
+
75
+ ## `.labelText` descender clipping (Matt Massey, 2026-08-28)
76
+
77
+ `.labelText` used plain `overflow: hidden` to make `text-overflow: ellipsis` work, which also
78
+ clips descenders (e.g. the "g" in a long label) whenever `text_line-height` is tighter than the
79
+ font's natural ascent+descent. Switched to `overflow: clip; overflow-clip-margin: 0.35em;` — same
80
+ truncation, but ink can bleed slightly past the line box before it's actually clipped. `.root`'s
81
+ own `overflow: hidden` (the max-width truncation bounding box) is untouched — it has padding
82
+ around the label so it isn't tight against the glyphs the way `.labelText` is. Project-wide fix;
83
+ see Chip's `CHIP_IMPLEMENTATION_NOTES.md` for the original discovery.
@@ -8,5 +8,5 @@ The `Dropdown` component is mapped explicitly to Mantine's `<Select>` following
8
8
  4. **Popup Vertical Padding:** The gap above/below the option list inside `.dropdown` is explicitly set from the same `--recursica_..._dropdown_properties_vertical-padding` token the closed control uses — it was previously left to Mantine's own untokenized `--combobox-padding` (4px) default.
9
9
  5. **Clear Button Styling:** Mantine's native clear button (`clearButtonProps`, shown when `clearable` + a value are both present) is a bare `CloseButton` with its own hardcoded gray icon/hover styling by default. `Dropdown.tsx` merges in a `.clearButton` class (Dropdown.module.css) that overrides it with the same icon-size/trailing-icon-color/focus-ring tokens as the rest of the right section, using the double-class-selector specificity trick (same as Chip.module.css's `.root.root`) to beat Mantine's own CSS module rule without `!important`.
10
10
  6. **Rich Option Content (`leadingIcon`/`supportingText`):** `data` items now accept optional `leadingIcon`/`supportingText` fields, via the shared `RecursicaComboboxItem` type in `@recursica/adapter-common` (see `MANTINE_ADAPTER_RICH_OPTION_DATA.md` at the repo root) — the same type `AutoComplete` and both `mui-adapter` components use, so it's declared once and not redeclared per component/adapter. `label` on that shared type is optional, falling back to `value` (matches Mantine's own runtime default for both `Select` and `Autocomplete`). `Dropdown.tsx` installs a default `renderOption` (`../../utils/renderRichOption.tsx`, shared with `AutoComplete`) that reads `leadingIcon`/`supportingText` straight off Mantine's own parsed `option` — no separate lookup-by-value map is needed, since Mantine's `getParsedComboboxData` passes extra fields on an item through untouched whenever the item already has both `value` and `label`. Because `label` is now optional, `data` is first run through adapter-common's `normalizeComboboxData` (backfilling `label` from `value`) before being handed to Mantine, so items missing `label` don't have their `leadingIcon`/`supportingText` silently dropped by that same parser (see `AutoComplete.tsx`'s identical, longer-standing use of this — `Dropdown`'s `label` used to be required, which is why it didn't need this before). A caller-supplied `renderOption` always wins over the default. New CSS classes (`.optionContent`/`.optionIcon`/`.optionText`/`.optionSupportingText`) reuse the menu-item component's icon/supporting-text tokens — no dedicated dropdown-option tokens exist for either, same reasoning as the `.option[data-selected]` reuse above. The icon is only rendered when `leadingIcon` is present (a conditional child, not a hidden reserved slot), so label/supportingText shift left when there's no icon; `.optionContent`'s `align-items: center` keeps the label vertically centered when there's no `supportingText` to stack under it.
11
- 7. **`wrapItemText`:** `label`/`supportingText` default to single-line truncation with an ellipsis (`.optionText > *` — `overflow: hidden; text-overflow: ellipsis; white-space: nowrap`). Passing `wrapItemText` adds `.optionTextWrap` alongside `.optionText`, re-enabling wrapping (`white-space: normal; overflow-wrap: anywhere`) for both children — later-cascade-wins, equal specificity, same mechanism as this file's other CSS overrides. `renderRichOption`/`renderRichOptionContent` take `wrapItemText` as a third parameter and combine the two class names when it's true.
11
+ 7. **`wrapItemText`:** `label`/`supportingText` default to single-line truncation with an ellipsis (`.optionText > *` — `overflow: clip; overflow-clip-margin: 0.35em; text-overflow: ellipsis; white-space: nowrap`). Passing `wrapItemText` adds `.optionTextWrap` alongside `.optionText`, re-enabling wrapping (`white-space: normal; overflow-wrap: anywhere`) for both children — later-cascade-wins, equal specificity, same mechanism as this file's other CSS overrides. `renderRichOption`/`renderRichOptionContent` take `wrapItemText` as a third parameter and combine the two class names when it's true. `.optionText > *` used plain `overflow: hidden` until 2026-08-28 (Matt Massey) — it clipped descenders (e.g. "g") whenever `text_line-height` is tighter than the font's natural ascent+descent; `overflow-clip-margin` gives ink a small bleed allowance while still clipping genuinely overflowing text, same project-wide fix as Chip's `CHIP_IMPLEMENTATION_NOTES.md`.
12
12
  8. **Selected Option Highlight (bug fix):** The `.option[data-selected="true"], .option[data-combobox-active="true"]` background/text-color rule (and the matching `.optionIcon`/`.optionSupportingText` color rules) used to key off `data-combobox-selected` instead of `data-combobox-active`. Despite the name, `data-combobox-active` is what Mantine sets when an option's value matches the current field value (`OptionsDropdown.mjs`: `active: checked`, consumed by `ComboboxOption.mjs`'s `mod` map); `data-combobox-selected` is an unrelated, transient keyboard-navigation highlight that Mantine sets/clears imperatively via `element.setAttribute` outside React (`use-combobox.mjs`'s `selectOption`/`clearSelectedItem`), not tied to the chosen value at all. The bug: the real selected option only showed the brand background while being arrow-key-navigated, and lost it entirely on a normal open/close (matches Playwright verification — `data-combobox-active="true"` is present and gets the token background after a plain click-select-reopen, with no keyboard involved).
@@ -408,7 +408,10 @@
408
408
 
409
409
  /* Default: label/supportingText each truncate to a single line with an ellipsis. */
410
410
  .optionText > * {
411
- overflow: hidden;
411
+ overflow: clip; /* HARDCODE: `hidden` clips descenders (e.g. "g") when text_line-height is
412
+ tighter than the font's natural ascent+descent; overflow-clip-margin gives ink a small bleed
413
+ allowance while still clipping genuinely overflowing text (see Chip's IMPLEMENTATION_NOTES.md). */
414
+ overflow-clip-margin: 0.35em;
412
415
  text-overflow: ellipsis;
413
416
  white-space: nowrap;
414
417
  }
@@ -16,7 +16,12 @@ Mantine internally handles scroll state natively, dynamically showing/hiding a d
16
16
 
17
17
  ### 3. Title truncation
18
18
 
19
- `.title` truncates with an ellipsis (`overflow: hidden`, `white-space: nowrap`, `text-overflow: ellipsis`) rather than wrapping. It also needs `flex: 1 1 auto; min-width: 0;` since it's a flex child of `.header` alongside the close button — without `min-width: 0`, a flex item won't shrink below its content's intrinsic width, so ellipsis never engages. `.header`'s `display: flex` is likewise explicit rather than relied upon from Mantine's own header class, so the mui-adapter's plain-`<div>` header gets identical layout.
19
+ `.title` truncates with an ellipsis (`overflow: clip; overflow-clip-margin: 0.35em`, `white-space: nowrap`, `text-overflow: ellipsis`) rather than wrapping. It also needs `flex: 1 1 auto; min-width: 0;` since it's a flex child of `.header` alongside the close button — without `min-width: 0`, a flex item won't shrink below its content's intrinsic width, so ellipsis never engages. `.header`'s `display: flex` is likewise explicit rather than relied upon from Mantine's own header class, so the mui-adapter's plain-`<div>` header gets identical layout.
20
+
21
+ `.title` used plain `overflow: hidden` until 2026-08-28 (Matt Massey) — it clipped descenders
22
+ (e.g. "g" in a long title) whenever `text_line-height` is tighter than the font's natural
23
+ ascent+descent. `overflow-clip-margin` gives ink a small bleed allowance while still clipping
24
+ genuinely overflowing text, same project-wide fix as Chip's `CHIP_IMPLEMENTATION_NOTES.md`.
20
25
 
21
26
  ### 4. Width was pinned to Mantine's `md` size, not content-driven
22
27
 
@@ -78,7 +78,10 @@
78
78
  .title {
79
79
  flex: 1 1 auto; /* HARDCODE: let the title claim the space between the header edge and the close button */
80
80
  min-width: 0; /* HARDCODE: required for text-overflow ellipsis to take effect on a flex child */
81
- overflow: hidden;
81
+ overflow: clip; /* HARDCODE: `hidden` clips descenders (e.g. "g") when text_line-height is
82
+ tighter than the font's natural ascent+descent; overflow-clip-margin gives ink a small bleed
83
+ allowance while still clipping genuinely overflowing text (see Chip's IMPLEMENTATION_NOTES.md). */
84
+ overflow-clip-margin: 0.35em;
82
85
  white-space: nowrap;
83
86
  text-overflow: ellipsis;
84
87
 
@@ -104,3 +104,13 @@ Mantine's Drawer content does not set `border-style` natively. Without this, the
104
104
  - **Scrollable** — Internal scrollbar enabled when content exceeds the panel height. Header and footer CTAs remain pinned.
105
105
 
106
106
  Mantine's Drawer handles this automatically — the `body` section scrolls when content overflows, while the `header` remains fixed. The `Panel.Footer` uses `margin-top: auto` to stay at the bottom.
107
+
108
+ ---
109
+
110
+ ## `.titleTruncate` descender clipping (Matt Massey, 2026-08-28)
111
+
112
+ `.titleTruncate` used plain `overflow: hidden` to make `text-overflow: ellipsis` work, which also
113
+ clips descenders (e.g. the "g" in a long title) whenever `text_line-height` is tighter than the
114
+ font's natural ascent+descent. Switched to `overflow: clip; overflow-clip-margin: 0.35em;` — same
115
+ truncation, but ink can bleed slightly past the line box before it's actually clipped.
116
+ Project-wide fix; see Chip's `CHIP_IMPLEMENTATION_NOTES.md` for the original discovery.
@@ -96,7 +96,10 @@
96
96
  .titleTruncate {
97
97
  composes: title;
98
98
  white-space: nowrap;
99
- overflow: hidden;
99
+ overflow: clip; /* HARDCODE: `hidden` clips descenders (e.g. "g") when text_line-height is
100
+ tighter than the font's natural ascent+descent; overflow-clip-margin gives ink a small bleed
101
+ allowance while still clipping genuinely overflowing text (see Chip's IMPLEMENTATION_NOTES.md). */
102
+ overflow-clip-margin: 0.35em;
100
103
  text-overflow: ellipsis;
101
104
  display: block;
102
105
  flex: 1;
@@ -0,0 +1,12 @@
1
+ # Text – Implementation Notes
2
+
3
+ ## `.root` `text-wrap: balance` (Matt Massey, 2026-08-28)
4
+
5
+ **Decision:** Added `text-wrap: balance` via a new `Text.module.css` `.root` class, merged onto the
6
+ typography class alongside the caller's own `className`.
7
+
8
+ **Implementation:** UX asked for more evenly balanced multi-line wrapping instead of a ragged last
9
+ line. Not a design token — it's a layout algorithm choice, so it's hardcoded rather than pulled
10
+ from `recursica_variables_scoped.css`. Chromium/Firefox only balance up to ~6 lines; longer
11
+ paragraphs silently fall back to normal wrapping past that point. No fallback needed — browsers
12
+ that don't support the value just ignore the declaration.
@@ -0,0 +1,13 @@
1
+ /*
2
+ * HARDCODED VALUES
3
+ * - `.root` `text-wrap: balance` — not a design token; a layout algorithm choice requested by
4
+ * UX (Matt Massey, 2026-08-28) to even out wrapped line lengths. See TEXT_IMPLEMENTATION_NOTES.md.
5
+ */
6
+
7
+ .root {
8
+ /* HARDCODE: balances wrapped line lengths instead of leaving a ragged short last line. Most
9
+ effective on short text; browsers cap balancing at ~6 lines, so long paragraphs silently
10
+ fall back to normal wrapping past that point — no fallback needed, unsupported browsers
11
+ just ignore the declaration. */
12
+ text-wrap: balance;
13
+ }
@@ -10,6 +10,7 @@ import {
10
10
  } from "../../utils/filterStylingProps";
11
11
 
12
12
  import { type RecursicaTextProps } from "@recursica/adapter-common";
13
+ import styles from "./Text.module.css";
13
14
 
14
15
  export type TextProps = RecursicaOverStyled<
15
16
  Omit<MantineTextProps, "variant"> & RecursicaTextProps
@@ -24,9 +25,9 @@ const _Text = forwardRef<HTMLDivElement, TextProps>(function Text(
24
25
  .className as string | undefined;
25
26
 
26
27
  const typographyClass = `recursica_brand_typography_${variant}`;
27
- const mergedClassName = classNameProp
28
- ? `${typographyClass} ${classNameProp}`
29
- : typographyClass;
28
+ const mergedClassName = [typographyClass, styles.root, classNameProp]
29
+ .filter(Boolean)
30
+ .join(" ");
30
31
 
31
32
  return (
32
33
  <MantineText
@@ -0,0 +1,12 @@
1
+ # Title – Implementation Notes
2
+
3
+ ## `.root` `text-wrap: balance` (Matt Massey, 2026-08-28)
4
+
5
+ **Decision:** Added `text-wrap: balance` via a new `Title.module.css` `.root` class, merged onto
6
+ the typography class for every `order` (h1–h6), alongside the caller's own `className`.
7
+
8
+ **Implementation:** UX asked for more evenly balanced multi-line wrapping instead of a ragged last
9
+ line — headings are the primary intended use case for this property. Not a design token — it's a
10
+ layout algorithm choice, so it's hardcoded rather than pulled from `recursica_variables_scoped.css`.
11
+ Chromium/Firefox only balance up to ~6 lines, which comfortably covers heading text. No fallback
12
+ needed — browsers that don't support the value just ignore the declaration.
@@ -0,0 +1,13 @@
1
+ /*
2
+ * HARDCODED VALUES
3
+ * - `.root` `text-wrap: balance` — not a design token; a layout algorithm choice requested by
4
+ * UX (Matt Massey, 2026-08-28) to even out wrapped line lengths. See TEXT_IMPLEMENTATION_NOTES.md.
5
+ */
6
+
7
+ .root {
8
+ /* HARDCODE: balances wrapped line lengths instead of leaving a ragged short last line. Most
9
+ effective on short text; browsers cap balancing at ~6 lines, so long paragraphs silently
10
+ fall back to normal wrapping past that point — no fallback needed, unsupported browsers
11
+ just ignore the declaration. */
12
+ text-wrap: balance;
13
+ }
@@ -10,6 +10,7 @@ import {
10
10
  } from "../../utils/filterStylingProps";
11
11
 
12
12
  import { type RecursicaTitleProps } from "@recursica/adapter-common";
13
+ import styles from "./Title.module.css";
13
14
 
14
15
  export type TitleProps = RecursicaOverStyled<
15
16
  Omit<MantineTitleProps, "size"> & RecursicaTitleProps
@@ -36,9 +37,9 @@ export const Title = forwardRef<HTMLHeadingElement, TitleProps>(function Title(
36
37
  .className as string | undefined;
37
38
 
38
39
  const typographyClass = `recursica_brand_typography_h${order}`;
39
- const mergedClassName = classNameProp
40
- ? `${typographyClass} ${classNameProp}`
41
- : typographyClass;
40
+ const mergedClassName = [typographyClass, styles.root, classNameProp]
41
+ .filter(Boolean)
42
+ .join(" ");
42
43
 
43
44
  return (
44
45
  <MantineTitle