@nubisco/ui 3.2.0 → 3.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nubisco/ui",
-  "version": "3.2.0",
+  "version": "3.4.0",
   "description": "Vue 3 UI component library",
   "packageManager": "pnpm@11.0.8",
   "repository": {

package/src/styles/_reset.scss

@@ -84,6 +84,11 @@
   a {
     background-color: transparent;
     all: unset;
+    /* `all: unset` resets box-sizing to content-box, and the element
+     * selector outranks the `*` border-box rule above, so every anchor
+     * (including link-rendered components like NbCard) would overflow the
+     * box its layout gave it by its own padding and border. */
+    box-sizing: border-box;
   }
 
   /**

package/src/styles/_theme.scss

@@ -146,6 +146,23 @@
     --nb-c-primary-hover-a11y: var(--nb-c-grape-hyacinth-600-a11y);
     --nb-c-primary-active: var(--nb-c-grape-hyacinth-700);
     --nb-c-primary-active-a11y: var(--nb-c-grape-hyacinth-700-a11y);
+    // A pale wash of the brand, for an edge drawn ON a primary fill (the
+    // ghost button's hover border is the only consumer today). It was
+    // var(--nb-c-grape-hyacinth-200) at the call site, which forced a
+    // white-label product to name the vendor's ramp in its own stylesheet.
+    //
+    // Derived, not aliased: an alias would still be violet after a product
+    // sets --nb-c-primary, which is the exact leak this token exists to
+    // close. 39% of the brand on white measures dE2000 0.71 from the tint
+    // it replaced, under the ~1.0 just-noticeable threshold, so no shipped
+    // hover border visibly moves. The dark theme repeats the mix at 50%
+    // because its --nb-c-primary is already a lighter step of the same ramp
+    // and needs less white to land on the same wash (dE2000 0.00 there).
+    --nb-c-primary-subtle: color-mix(
+      in srgb,
+      var(--nb-c-primary) 39%,
+      var(--nb-c-white)
+    );
 
     --nb-c-secondary: var(--nb-c-plain-black-700);
     --nb-c-secondary-a11y: var(--nb-c-plain-black-700-a11y);
@@ -249,6 +266,59 @@
     --nb-c-status-warning: var(--nb-c-phoenix-flames-700);
     --nb-c-status-error: var(--nb-c-chicken-comb-600);
 
+    // == Data visualisation roles ==========================================
+    // Charts address colour by ROLE, never by ramp: a series is "chart-3",
+    // not "emerald". The eight defaults below alias exactly the ramps that
+    // Charts/shared/palette.ts used to name inline, so this theme repaints
+    // nothing, but a white-label product now retints every chart in the
+    // product by redefining eight custom properties in one place instead of
+    // hardcoding hex per app. (A green-branded white-label product did the
+    // hardcoding and shipped a violet placeholder series.)
+    //
+    // Order is part of the contract. colorAt() walks 1, 2, 3 ... and wraps
+    // at 8, so the sequence has to degrade gracefully: the low roles are the
+    // best separated pair we have. Minimum CIEDE2000 across the first five
+    // roles is 16.0 under normal vision; across all eight it falls to 6.5,
+    // because roles 1 and 7 are both violet-blues. Under simulated
+    // deuteranopia the same numbers are 5.2 and 0.8. That is a property of
+    // the brand ramps, not of this indirection, and it is why the docs cap
+    // colour-only encoding at five series. See charts/color.md.
+    //
+    // Contrast against layer-1, in order: 7.28, 5.25, 3.16, 2.06, 4.62,
+    // 5.68, 7.04, 4.63. Two roles miss WCAG 1.4.11 at 3:1 here: role 4
+    // (amber) on every layer, and role 3 on layer-0 and layer-2 (2.85 and
+    // 2.69, it only clears on layer-1). Both stay because raising them
+    // would repaint charts already in production, and both are documented
+    // as fill-only, never a 1px line or a legend dot on its own.
+    // Re-measure any change with tests/chartRoles.test.ts.
+    --nb-c-chart-1: var(--nb-c-grape-hyacinth-500);
+    --nb-c-chart-2: var(--nb-c-the-blues-brothers-500);
+    --nb-c-chart-3: var(--nb-c-emerald-reflection-600);
+    --nb-c-chart-4: var(--nb-c-phoenix-flames-500);
+    --nb-c-chart-5: var(--nb-c-chicken-comb-500);
+    --nb-c-chart-6: var(--nb-c-liberty-blue-500);
+    --nb-c-chart-7: var(--nb-c-powder-blue-500);
+    --nb-c-chart-8: var(--nb-c-nouveau-gray-500);
+
+    // Sequential ramp anchors: one hue, lightness carries the magnitude.
+    // Interpolated at paint time by sequentialAt() in the chart palette
+    // module, so a retint of these two ends retints the whole ramp. In this
+    // theme the largest value is the darkest end (L* 87.4 down to 21.2),
+    // which inverts under .dark.
+    --nb-c-chart-sequential-from: var(--nb-c-grape-hyacinth-100);
+    --nb-c-chart-sequential-to: var(--nb-c-grape-hyacinth-700);
+
+    // Diverging ramp anchors: two hues meeting at a neutral zero point.
+    // Cool to warm rather than green to red, because a green/red pair is
+    // the one axis a deuteranope cannot read at all, and a diverging scale
+    // has no legend position to fall back on. The two ends are matched in
+    // lightness (L* 44.4 and 47.9) so neither pole looks heavier than the
+    // other, and the midpoint is near the page ground so zero reads as
+    // "nothing here".
+    --nb-c-chart-diverging-low: var(--nb-c-the-blues-brothers-500);
+    --nb-c-chart-diverging-mid: var(--nb-c-nouveau-gray-150);
+    --nb-c-chart-diverging-high: var(--nb-c-chicken-comb-500);
+
     // ── Node graph (NbBlueprint) ──────────────────────────────────────────
     // A port is a control, and it sits OUTSIDE the card on the canvas
     // ground, so its outline is measured against layer-0 rather than the
@@ -454,6 +524,10 @@
       var(--nb-c-black)
     );
     --nb-shell-sidebar-width: calc(var(--nb-base-unit) * 7); // 56px
+    // The verbose variant's rail width. A token rather than a literal inside
+    // Shell.vue's variant rule, so a product with long navigation labels can
+    // widen the rail without re-declaring the variant.
+    --nb-shell-sidebar-width-verbose: calc(var(--nb-base-unit) * 30); // 240px
     --nb-shell-sidebar-link-color: color-mix(
       in srgb,
       var(--nb-c-white) 55%,
@@ -483,15 +557,70 @@
       var(--nb-c-white)
     );
     --nb-shell-topbar-height: calc(var(--nb-base-unit) * 6.25); // 50px
+
+    // Shell chrome. Every rule that paints the frame reads one of these, so a
+    // dark or white-label product retints the shell by setting a token on
+    // :root instead of out-specifying Shell.vue's scoped [data-v-] selectors
+    // from a built stylesheet. The defaults point at the semantic tokens the
+    // chrome already used, so the pixels are unchanged, and because var()
+    // resolves where it is used they follow the .dark theme with no dark-mode
+    // duplicate of this block.
+    //
+    // Three levels: --nb-shell-bg for the frame ground, --nb-shell-chrome-* as
+    // the one place to retint every strip at once, and the per-region tokens
+    // that default to the chrome ones for when only the topbar should differ.
+    --nb-shell-bg: var(--nb-c-surface-raised);
+    --nb-shell-chrome-bg: var(--nb-c-surface);
+    --nb-shell-chrome-color: var(--nb-c-text);
+    --nb-shell-chrome-border: 1px solid var(--nb-c-border);
+    --nb-shell-chrome-padding-x: calc(var(--nb-base-unit) * 3); // 24px
+    --nb-shell-topbar-bg: var(--nb-shell-chrome-bg);
+    --nb-shell-topbar-color: var(--nb-shell-chrome-color);
+    --nb-shell-topbar-border: var(--nb-shell-chrome-border);
+    --nb-shell-fixedbar-bg: var(--nb-shell-chrome-bg);
+    --nb-shell-fixedbar-color: var(--nb-shell-chrome-color);
+    --nb-shell-fixedbar-border: var(--nb-shell-chrome-border);
+    // Shared by the outer menu, the inner menu and the legacy menubar: they
+    // are one visual family and no application has ever wanted them to differ.
+    --nb-shell-menu-bg: var(--nb-shell-chrome-bg);
+    --nb-shell-menu-color: var(--nb-shell-chrome-color);
+    --nb-shell-menu-border: var(--nb-shell-chrome-border);
+    --nb-shell-body-bg: var(--nb-shell-chrome-bg);
+    // The page ground behind the main region. Kept separate from the chrome:
+    // a branded topbar usually sits above an unbranded page.
+    --nb-shell-main-bg: var(--nb-c-surface);
     --nb-shell-inspector-width: calc(var(--nb-base-unit) * 70); // 560px
     --nb-shell-inspector-expanded-width: 50vw;
+    // Ceiling for a visible inspector, whatever set its width (a size preset,
+    // the expanded flag, or a dragged width). Half the viewport is the point
+    // at which the inspector stops being a side panel and starts being the
+    // page. Set it to `none` to opt out.
+    // `max()` with the resize floor is load-bearing: half a 560px-wide window
+    // is 280px, below the 288px floor the resize handle announces and clamps
+    // to, so a bare 50vw made the announced value, the clamped value and the
+    // rendered width disagree on a narrow viewport. The floor wins there.
+    --nb-shell-inspector-max-width: max(calc(var(--nb-base-unit) * 36), 50vw);
     --nb-shell-inspector-border: 1px solid var(--nb-c-border);
     --nb-shell-inspector-bg: var(--nb-c-surface);
+    // The grab-line on the inspector's resize handle. A token, not a literal
+    // brand hex: a white-label product should never have to name the vendor's
+    // ramp to restyle the frame.
+    --nb-shell-inspector-resize-color: var(--nb-c-primary);
+    // The dimmer behind the navigation drawer at collapsed widths. Black at
+    // 45% reads on both themes because it darkens whatever is under it rather
+    // than painting a colour of its own.
+    --nb-shell-scrim-bg: color-mix(in srgb, var(--nb-c-black) 45%, transparent);
 
     // Panels — emitted at :root so consumer apps can override on :root without
     // fighting the components' scoped-style specificity.
     --nb-shell-panel-header-height: calc(var(--nb-base-unit) * 3.5); // 28px
     --nb-shell-panel-gap: 1px; // hairline separator, not a spacing step
+    --nb-shell-panel-bg: var(--nb-c-surface);
+    --nb-shell-panel-border: 1px solid var(--nb-c-border);
+    // Transparent by default so the header reads as part of the panel; set it
+    // when a product wants the header bar tinted against its own content.
+    --nb-shell-panel-header-bg: transparent;
+    --nb-shell-panel-header-border: 1px solid var(--nb-c-border);
     --nb-bottom-panel-header-height: calc(var(--nb-base-unit) * 3.5); // 28px
     --nb-bottom-panel-bg: var(--nb-c-layer-0, var(--nb-c-bg));
     --nb-bottom-panel-border: var(--nb-c-border);
@@ -506,6 +635,13 @@
   .dark {
     // Status colors — lighter tints for dark backgrounds
     --nb-c-primary: #{colors.get-color('grape-hyacinth', 400)};
+    // Same wash, re-mixed: the dark --nb-c-primary is a 400, so it takes less
+    // white than the light 500 does to reach the tint this token used to alias.
+    --nb-c-primary-subtle: color-mix(
+      in srgb,
+      var(--nb-c-primary) 50%,
+      var(--nb-c-white)
+    );
     --nb-c-primary-a11y: #{colors.color-contrast(
         colors.get-color('grape-hyacinth', 400)
       )};
@@ -634,6 +770,41 @@
     --nb-c-status-warning: #{colors.get-color('phoenix-flames', 400)};
     --nb-c-status-error: #{colors.get-color('chicken-comb', 300)};
 
+    // Data visualisation roles, dark. Same eight hues, stepped up their
+    // ramps, exactly as --nb-c-primary and the status colours are stepped
+    // here. The light values are mid-ramp fills chosen against a white
+    // page: three of them (roles 1, 6 and 7 at 2.17, 2.78 and 2.25 against
+    // layer-1) sink into a dark one and were failing WCAG 1.4.11 in every
+    // dark-mode chart the fleet renders. The tints below measure 5.48,
+    // 4.42, 7.69, 8.89, 4.32, 4.30, 4.49 and 5.56 against layer-1, and all
+    // eight clear 3:1 on layer-0 through layer-2, which the light set does
+    // not manage. They do NOT clear it on layer-3, the lightest dark
+    // surface (roles 2, 5, 6 and 7 land between 2.79 and 2.92), so do not
+    // paint a chart on layer-3 in dark without overriding these. Role 7 is
+    // a 350 rather than the 400 its neighbours use: at 400 it measured
+    // 2.95 on layer-2, and contrast wins over separation on the role that
+    // is already the weakest of the eight. Minimum CIEDE2000 is 15.4 over
+    // the first five roles and 5.5 over all eight.
+    --nb-c-chart-1: var(--nb-c-grape-hyacinth-300);
+    --nb-c-chart-2: var(--nb-c-the-blues-brothers-400);
+    --nb-c-chart-3: var(--nb-c-emerald-reflection-500);
+    --nb-c-chart-4: var(--nb-c-phoenix-flames-400);
+    --nb-c-chart-5: var(--nb-c-chicken-comb-400);
+    --nb-c-chart-6: var(--nb-c-liberty-blue-400);
+    --nb-c-chart-7: var(--nb-c-powder-blue-350);
+    --nb-c-chart-8: var(--nb-c-nouveau-gray-400);
+
+    // Sequential runs the other way on a dark page: the largest value is
+    // the brightest end, so "from" is the tint nearest the background.
+    --nb-c-chart-sequential-from: var(--nb-c-grape-hyacinth-800);
+    --nb-c-chart-sequential-to: var(--nb-c-grape-hyacinth-200);
+
+    // Diverging keeps its two hues and moves the zero point to a dark
+    // neutral. Ends stepped one tint lighter to hold 4.3:1 on layer-1.
+    --nb-c-chart-diverging-low: var(--nb-c-the-blues-brothers-400);
+    --nb-c-chart-diverging-mid: var(--nb-c-nouveau-gray-800);
+    --nb-c-chart-diverging-high: var(--nb-c-chicken-comb-400);
+
     // Discrete
     --nb-c-discrete: #{colors.get-color('nouveau-gray', 700)};
     --nb-c-component-discrete-text: #{colors.get-color('nouveau-gray', 300)};

package/src/styles/directives/_tooltip.scss

@@ -1,24 +1,101 @@
 @mixin tooltip {
+  // The description node. Not a chip: it is the text of the tooltip as
+  // assistive technology sees it, present from the moment the binding mounts,
+  // referenced by the anchor's `aria-describedby` the whole time.
+  //
+  // Visually hidden, never `display: none` and never the `hidden` attribute.
+  // Both of those remove it from the accessibility tree, which is the one
+  // place it has to be; the whole reason it exists is that a description
+  // computed at focus time cannot be waiting on a hover-intent timer.
+  .nb-tooltip-description {
+    position: absolute;
+    inset-block-start: 0;
+    inset-inline-start: 0;
+    inline-size: 1px;
+    block-size: 1px;
+    padding: 0;
+    margin: 0;
+    border: 0;
+    overflow: hidden;
+    // `clip-path` rather than the legacy `clip`: it is not deprecated and it
+    // does not force the element out of the flow in a way that some engines
+    // use to skip it entirely.
+    clip-path: inset(50%);
+    white-space: nowrap;
+    pointer-events: none;
+  }
+
   .nb-tooltip {
     position: fixed;
     overflow: visible;
-    padding: var(--nb-base-unit);
+    // Logical, so a chip in an Arabic or Hebrew build gets its padding on the
+    // sides the text actually starts and ends on. The arrow offsets further
+    // down stay physical on purpose: placement is computed from geometry in
+    // the directive (which side has room), and geometry has no direction.
+    padding-block: var(--nb-base-unit);
+    padding-inline: var(--nb-base-unit);
     border-radius: calc(var(--nb-base-unit) / 1.333);
-    background: var(--nb-c-discrete);
-    color: var(--nb-c-discrete-a11y);
+    // Inverted surface, not the discrete grey pair. Two reasons: the grey
+    // pair only flips its background between themes (its -a11y foreground
+    // stays the light-theme value, so a dark-theme chip was dark text on a
+    // dark chip), and every hand-rolled tooltip in the fleet, including the
+    // two inside this library, independently chose an inverted chip. The two
+    // vars let a consumer retint one chip without touching the theme.
+    background: var(--nb-tooltip-bg, var(--nb-c-contrast));
+    color: var(--nb-tooltip-fg, var(--nb-c-surface));
     z-index: var(--nb-zindex-tooltip);
     text-transform: none;
     font-size: var(--nb-font-size-13);
-    line-height: 1;
-    user-select: none;
-    pointer-events: none;
+    // A chip has no width of its own: it shrink-wraps its text. Without a
+    // ceiling, a 400-character body renders as ONE line wider than the
+    // viewport, and the directive's clamp cannot rescue it (the maximum left
+    // goes negative, so the chip is pushed back to the inset and runs off the
+    // right edge). 34 base units is about 55 characters at this size, a
+    // comfortable measure. `--nb-tooltip-max-width` widens or narrows it for
+    // one chip; the answer for anything that needs much more is not a
+    // tooltip.
+    max-inline-size: var(
+      --nb-tooltip-max-width,
+      calc(var(--nb-base-unit) * 34)
+    );
+    // Now that the text can wrap, it needs leading. At `line-height: 1` a
+    // wrapped body, a documented `<br>` and an embedded newline all render as
+    // touching lines.
+    line-height: var(--nb-line-height-snug);
+    // A single unbroken token (a URL, a hash, a file path) would otherwise
+    // blow straight through the max-width.
+    overflow-wrap: anywhere;
+    // The chip is reachable by the pointer. WCAG 2.1 AA 1.4.13 ("Hoverable")
+    // requires that content revealed on hover can be hovered without
+    // disappearing, and `pointer-events: none` makes that impossible by
+    // construction: nothing the user does with the mouse can ever land on the
+    // chip. That is not a defensible default for the one affordance in this
+    // library whose whole purpose is labelling controls, and it is the
+    // difference between readable and unreadable for anyone at 200% zoom, who
+    // has to pan onto a clamped chip to finish the sentence.
+    //
+    // The directive supplies the other half: entering the chip cancels the
+    // pending hide, leaving it restarts it. The chip stays out of the tab
+    // order and holds nothing operable, so it is still not a container.
+    pointer-events: auto;
+    // Text in a chip is often the thing worth copying: an error code, a full
+    // path, a signature. There is no reason to forbid selecting it now that
+    // the pointer can reach it.
+    user-select: text;
+    // Structural containment, defence in depth for caller-supplied content.
+    // `contain: layout` makes the chip the containing block for any
+    // absolutely or fixed-positioned descendant, so a class or a style that
+    // reached the chip from a CMS field or an API payload cannot escape the
+    // chip's box to become a full-viewport overlay. The content sanitiser
+    // already refuses `position`; this is the belt to that pair of braces,
+    // and it does not clip (the arrow pseudo-elements still overflow).
+    contain: layout;
     opacity: 0;
-    text-align: center;
-    --tooltip-arrow-border-color: var(--nb-c-discrete);
-    transform: scale(0.95);
-    transition:
-      opacity 0.2s ease,
-      transform 0.2s ease;
+    // `start`, not `center`. A one-line chip shrink-wraps its text so the two
+    // are indistinguishable, and a wrapped chip is far easier to read ragged
+    // right than centred.
+    text-align: start;
+    --tooltip-arrow-border-color: var(--nb-tooltip-bg, var(--nb-c-contrast));
     &:before,
     &:after {
       position: absolute;
@@ -47,32 +124,64 @@
     }
     &-tip {
       font-weight: var(--nb-font-weight-regular);
-      color: var(--nb-c-component-discrete-text);
+      // Demoted by transparency rather than by a second colour token: on an
+      // inverted chip any fixed grey is right in one theme and wrong in the
+      // other, while 78% of an already-contrasting foreground stays legible
+      // in both.
+      opacity: 0.78;
     }
 
+    // Every flavour foreground is the theme's auto-contrast companion for its
+    // own background, never a literal. `--nb-c-danger` and friends are not the
+    // same colour in both themes (the dark theme uses a lighter step of the
+    // same ramp), so a hardcoded white is correct in at most one of them and
+    // is the WORST available choice in the other. The `-a11y` companions are
+    // computed from the background they sit on, which is why the rest of the
+    // library uses them.
     &-flavor {
       &-primary {
         background: var(--nb-c-primary);
-        color: var(--nb-c-white);
+        color: var(--nb-c-primary-a11y);
         --tooltip-arrow-border-color: var(--nb-c-primary);
         .nb-tooltip-tip {
-          color: var(--nb-c-white);
+          color: var(--nb-c-primary-a11y);
         }
       }
       &-danger {
         background: var(--nb-c-danger);
-        color: var(--nb-c-white);
+        color: var(--nb-c-danger-a11y);
         --tooltip-arrow-border-color: var(--nb-c-danger);
         .nb-tooltip-tip {
-          color: var(--nb-c-white);
+          color: var(--nb-c-danger-a11y);
         }
       }
       &-info {
         background: var(--nb-c-info);
-        color: var(--nb-c-white);
+        color: var(--nb-c-info-a11y);
         --tooltip-arrow-border-color: var(--nb-c-info);
         .nb-tooltip-tip {
-          color: var(--nb-c-white);
+          color: var(--nb-c-info-a11y);
+        }
+      }
+      // `success` and `warning` exist because the library's status vocabulary
+      // has them (NbBanner.status, EVariant) and the tooltip was the one place
+      // that silently did not: `flavor: 'warning'` used to compile and emit an
+      // unstyled chip. Same construction as the three above, so a themed build
+      // that moves the ramp moves these with it.
+      &-success {
+        background: var(--nb-c-success);
+        color: var(--nb-c-success-a11y);
+        --tooltip-arrow-border-color: var(--nb-c-success);
+        .nb-tooltip-tip {
+          color: var(--nb-c-success-a11y);
+        }
+      }
+      &-warning {
+        background: var(--nb-c-warning);
+        color: var(--nb-c-warning-a11y);
+        --tooltip-arrow-border-color: var(--nb-c-warning);
+        .nb-tooltip-tip {
+          color: var(--nb-c-warning-a11y);
         }
       }
     }
@@ -164,23 +273,36 @@
     }
   }
 
-  // Animation for appearing
+  @media (prefers-reduced-motion: reduce) {
+    .nb-tooltip {
+      animation: none !important;
+      transform: none;
+    }
+  }
+
+  // Entrance and exit. Both the fade and the small rise live in the keyframes
+  // rather than in a base `transform` plus a `transition`: the directive only
+  // ever sets `animation`, so a base transform had nothing to transition back
+  // from and every chip rendered permanently scaled down.
   @keyframes tooltipAppear {
     0% {
       opacity: 0;
+      transform: scale(0.96);
     }
     100% {
       opacity: 1;
+      transform: scale(1);
     }
   }
 
-  // Animation for disappearing
   @keyframes tooltipDisappear {
     0% {
       opacity: 1;
+      transform: scale(1);
     }
     100% {
       opacity: 0;
+      transform: scale(0.98);
     }
   }
 }