nuvox 0.1.4 → 0.1.5

package/BUILDING-COMPONENTS.md

@@ -437,6 +437,8 @@ good at telling you.
 | 42 | Carousel | F | ✅ | ❌ | ❌ *(own baseline: arrow keys, pause-on-hover, not Rule 11)* | ✅ | ✅ *(active slide)* | 🛠️ Built |
 | 43 | Rating | B | ✅ | ❌ | ❌ | ➖ | ✅ *(selected value)* | 🛠️ Built *(added outside the original plan — a single-value control, same shape as Slider)* |
 | 44 | StatCard | A | ✅ | ❌ | ❌ | ➖ | ❌ | 🛠️ Built *(added outside the original plan — composes `Card` for chrome)* |
+| 45 | CodeBlock | A | ✅ *(forwards to the scrollable `<pre>`)* | ❌ | ❌ | ➖ | ❌ | 🛠️ Built *(added outside the original plan — tokenizer lives in the shared `core/code-highlight.ts` primitive, not owned solely by this component; `highlighter` prop is a pluggable escape hatch, see that file's header)* |
+| 46 | RichTextEditor | F | ✅ *(`RichTextContent` forwards to the contentEditable element)* | ➖ *(the link editor's popover panel portals via the real `Popover`, not directly)* | ➖ *(inherited transitively through `Popover`)* | ✅ *(link editor composes `Popover`, Rule 12)* | ✅ *(`value`/`onChange`, HTML string)* | 🛠️ Built *(added outside the original plan — by far the largest component; deliberately NOT a ProseMirror-style document model, see `core/rich-text.ts`'s header for the v1 scope boundary and the `engine` escape hatch for consumers who need one)* |
 
 A few things worth noting from the table itself, not just the rows:
 

package/CHANGELOG.md

@@ -3,173 +3,77 @@
 All notable changes to this project are documented here.
 Format loosely follows [Keep a Changelog](https://keepachangelog.com/).
 
+## [0.1.5]
+
+### Added
+
+* Added new components: `ChatBubble`, `Sidebar`, `ResizablePanel`, `CodeBlock`, `RichTextEditor`, and `SpeedDial`.
+
+### Fixed
+
+* Fixed multiple CSS and theming issues across several components.
+* Improved component styling consistency across themes.
+* Fixed various layout, spacing, and visual issues.
+
 ## [0.1.4]
 
 ### Fixed
-- The `[data-nuvox-portal]` exemption added in 0.1.3 fixed a nested
-  overlay closing its own container, but was too broad: it exempted
-  a click inside ANY portal, including one belonging to a completely
-  unrelated SIBLING overlay that merely shares a common enclosing
-  overlay. Two `DropdownMenu`s both living inside the same `Popover`
-  are siblings of each other, not nested in each other — opening one
-  while the other was open left both on screen at once, only closing
-  on a re-click or a selection. `useClickOutside` now walks the real
-  relationship instead of doing a blanket portal check: it follows
-  "which portal contains this click" → "whose trigger opened that
-  portal" → "is that trigger contained in my own refs, or itself
-  inside another portal" (repeating for arbitrarily deep nesting) —
-  which correctly tells "genuinely nested inside me" apart from
-  "elsewhere inside a shared ancestor," however many levels deep.
-  `ThemedPortal` now tracks each portal's own anchor element for this
-  to walk. See the "Sibling overlays" and first two "Nested overlay"
-  cases in `tests/nested-overlays.test.tsx`.
-- A `DropdownMenu` (or `Select`/`Combobox`/`ColorPicker`) nested
-  inside an open `Popover` rendered BEHIND it: each component's CSS
-  sets a fixed z-index tier (`Popover` 1060, `DropdownMenu`/`Select`/
-  `Combobox` 1050, `Tooltip` 1100, `Toast` 1200, ...), correct for
-  independent, non-nested overlays but backwards for this one
-  relationship — the nested overlay needs to paint above its own
-  container regardless of which tier either belongs to. `ThemedPortal`
-  now detects when an overlay's own trigger sits inside another,
-  already-open overlay's portaled content, and in that case only,
-  assigns it an inline z-index above the shared 1150 base (below
-  `Toast`'s 1200, which stays on top of everything as a global
-  notification regardless of nesting) via `position: relative` on the
-  portal wrapper itself — not the component's own CSS class, so
-  ordinary non-nested overlays are completely untouched. Verified safe
-  for `Popover`/`DropdownMenu` specifically: both position their
-  content with inline `position: fixed` (`useFloatingPosition`), which
-  isn't affected by an ancestor's `position: relative` — only
-  `transform`/`filter`/etc. would change a fixed descendant's
-  containing block. Not verified against every possible pairing (e.g.
-  a `position: absolute` `Tooltip` ending up as the nested one) — this
-  covers the reported and tested composition, not every combination.
+
+* Fixed nested overlay interactions so genuinely nested overlays work correctly without interfering with sibling overlays.
+* Fixed z-index handling for nested overlays such as `DropdownMenu`, `Select`, `Combobox`, and `ColorPicker` inside other overlays.
+* Improved overlay behavior across deeply nested portal structures.
+* Added regression coverage for nested and sibling overlay scenarios.
 
 ## [0.1.3]
 
 ### Fixed
-- `neobrutalism`'s `warning.light` token (`#fef3c7`) was byte-identical
-  to the theme's own `background` — every warning `Alert`, and anything
-  else drawing from that token, rendered invisibly against the page.
-  Now `#fde68a`, one step further into the same warm-amber family.
-- `neobrutalism`'s `Rating` stars had no visible outline once filled:
-  the star icon's stroke and fill both come from `color`, so a filled
-  star's outline was purple-on-purple, not the black border every
-  other surface in this theme gets. Scoped override forces a black
-  stroke on all three star states (`neobrutalism` only).
-- `gradient`'s `text`/`textMuted` were still `light` theme's values,
-  measured at 2.79:1 and a barely-there 1.32:1 against the theme's own
-  background gradient's darker stop — anything rendered directly on
-  the page background (as `Timeline`/`Pagination`/`Tabs` are, per this
-  library's own docs examples, with no wrapping surface assumed) was
-  close to unreadable. Darkened both — see the measured before/after
-  in the new `tests/theme-text-contrast.test.ts`. `textMuted` still
-  can't clear full AA (4.5:1) against the gradient's darkest point
-  with a single flat color; this is the best available compromise,
-  not a complete fix.
-- `glass`'s `border` (`rgba(255,255,255,0.35)`) composited to literal
-  `#ffffff` against a plain white backdrop — a 1.0:1 ratio, i.e.
-  actually invisible (reported as `Progress`'s track outline
-  vanishing). Retinted to a neutral slate that stays visible against
-  both a plain white and a plain black fallback backdrop, since most
-  consumers won't add the "rich background" this theme's own
-  description says it needs.
-- `Slider`'s value-label bubble (`showValueLabel`) had no space
-  reserved for it above the track and could overflow into the field's
-  own `label` text above it — most visible with a thumb near 0%.
-  `getRootClasses` (internal, not part of the public API surface) now
-  takes `showValueLabel` and adds a modifier class that reserves the
-  room the bubble actually needs.
-- Nesting one dismissible overlay inside another (e.g. a `DropdownMenu`
-  inside a `Popover`) broke: every overlay portals its content to
-  `document.body` via `ThemedPortal`, as a DOM sibling of wherever it
-  was rendered rather than a descendant, so a click inside the nested
-  one registered as "outside" the outer one's own refs and closed it
-  before the click could register. `useClickOutside` now ignores
-  clicks inside any `[data-nuvox-portal]` node, fixing every
-  `Popover`/`DropdownMenu`/`Select`/`Combobox`/`ContextMenu`/
-  `CommandPalette` pairing at once instead of one at a time. See
-  `tests/nested-overlays.test.tsx`.
-- `Carousel`'s `CarouselPrevious`/`CarouselNext` centered against the
-  whole `.nx-carousel` box (viewport + indicators + anything else
-  below it), not the viewport alone — correct only by coincidence when
-  the viewport was tall relative to everything else in the box.
-  `.nx-carousel` is now a CSS grid with the viewport pinned to its own
-  grid cell, which becomes the containing block for a same-cell
-  absolutely-positioned item (CSS Grid §10.1). This holds regardless
-  of `CarouselIndicators`' height or the viewport's own height, so an
-  explicit height is no longer required for correct centering (still
-  good practice for layout stability, just not load-bearing anymore).
-  Wrapping the buttons in your own `<div>` is still unsupported, for a
-  different reason than before: a plain wrapper isn't a positioning
-  context, so the buttons fall through to `.nx-carousel` regardless of
-  the grid fix.
-- `docs-site`'s live "Controlled" `Carousel` demo and `carousel.mdx`'s
-  guidance both still reflected the pre-fix structure/requirements;
-  updated to match the fix above.
+
+* Fixed multiple theme contrast and visibility issues across `neobrutalism`, `gradient`, and `glass` themes.
+* Fixed `neobrutalism` warning colors and `Rating` star outlines.
+* Improved text contrast in the `gradient` theme.
+* Fixed `glass` theme borders becoming invisible on plain backgrounds.
+* Fixed `Slider` value labels overlapping with field labels.
+* Fixed nested dismissible overlays closing unexpectedly when interacting with their child overlays.
+* Fixed `Carousel` navigation buttons being incorrectly centered relative to the full carousel container.
+* Updated the carousel documentation and live examples to match the corrected behavior.
 
 ### Added
-- `tests/nested-overlays.test.tsx` — regression coverage for the
-  overlay-nesting fix above: fails against the old `useClickOutside`,
-  passes against the new one.
-- `tests/theme-text-contrast.test.ts` — checks `text`/`textMuted`
-  against `background` for every theme, including gradient stops
-  extracted from non-solid backgrounds. `outline-text-contrast.test.ts`
-  only ever checked the outline-button `color-mix()` blend and
-  explicitly skipped non-solid backgrounds — a real coverage gap; this
-  is what would have caught the `gradient` regression above before it
-  shipped.
+
+* Added regression tests for nested overlays and theme text contrast.
 
 ## [0.1.2]
 
 ### Fixed
-- `Select` now has a real `label` prop (previously only `aria-label`/
-  `aria-labelledby` — every other form field had `label`, this was the
-  one gap).
-- `Slider`'s `onChange` no longer forces the `number | readonly [number,
-  number]` union in single-thumb mode. It's now generic, so a plain
-  `<Slider value={n} onChange={setN} />` infers `(value: number) =>
-  void` with no cast needed; range mode still infers the tuple.
-- `nuvox/react` now re-exports ~20 prop-relevant types that previously
-  only lived in `"nuvox"` (`SliderValue`, `SelectOptionItem`,
-  `CommandItem`/`CommandGroup`, `TableCoreProps`, `DrawerSide`/
-  `DrawerSize`, `ModalSize`, `ProgressVariant`, and others) — a
-  consumer typing a handler no longer needs to import from both
-  entry points for one component.
+
+* Added the missing `label` prop to `Select`.
+* Improved `Slider` type inference for single-value and range modes.
+* Re-exported commonly used component prop types from `nuvox/react`.
 
 ### Changed
-- **Breaking:** `Accordion`, `Combobox`, `Select`, and `Tabs` renamed
-  `onValueChange` → `onChange`, unifying every controlled component in
-  the library on one convention (`onChange` was already the majority —
-  9 of 13 controlled components used it before this). No deprecated
-  alias was kept; see `CONTRACT.md` Rule 10 for why this was allowed
-  as a one-time pre-1.0 exception.
+
+* **Breaking:** Renamed `onValueChange` to `onChange` for `Accordion`, `Combobox`, `Select`, and `Tabs` to provide a consistent controlled-component API.
 
 ### Added
-- `docs-site/content/docs/css-variables.mdx` — a real reference page
-  for the theme system's CSS custom properties (`--color-background`,
-  `--color-text`, `--color-border`, etc.), previously only discoverable
-  incidentally inside `card.mdx`.
-- `tests/no-on-value-change.test.ts` — fails the build if
-  `onValueChange` is ever reintroduced as a real prop anywhere in
-  `src/react/`. Added after an external review caught the drift above;
-  this is the enforcement so it can't silently happen again.
-- `BUILDING-COMPONENTS.md`'s Category E section now explicitly states
-  the `value`/`onChange` convention applies there too — it previously
-  had no documented prop-naming rule at all for Tabs/Accordion's
-  controlled state, which is how they drifted differently from
-  Select/Combobox (Category D, which *did* already have this rule and
-  violated it).
+
+* Added dedicated documentation for theme CSS variables.
+* Added tests to prevent `onValueChange` from being reintroduced.
+* Updated component-building guidelines to document the `value` / `onChange` convention.
 
 ## [0.1.1]
 
-Published, but no record was kept of what changed from 0.1.0.
-If you're reading this after the fact: fill this in from `git log` /
-`npm diff nuvox@0.1.0 nuvox@0.1.1` before it's forgotten for good.
+### Fixed
+
+* Fixed multiple CSS and theming issues across several components.
+* Improved styling consistency and theme behavior throughout the component library.
+* Fixed various component-specific layout, spacing, and visual issues.
 
 ## [0.1.0]
 
-Initial public release. Single consolidated `nuvox` package (core +
-React bindings, previously split across 7 scoped `@nuvox/*` packages —
-all deprecated/unpublished as part of this release) with a
-framework-agnostic core, 40+ components, 11 themes, 490+ icons.
+Initial public release.
+
+* Consolidated the core and React bindings into a single `nuvox` package.
+* Deprecated and unpublished the previous 7 scoped `@nuvox/*` packages.
+* Introduced a framework-agnostic core with React bindings.
+* Added 40+ components.
+* Added 11 themes.
+* Added 490+ icons.