npm - @signal9/era-ui - Versions diffs - 21.0.0 → 23.0.0 - Mend

@signal9/era-ui 21.0.0 → 23.0.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.

Files changed (103) hide show

package/CHANGELOG.md CHANGED Viewed

@@ -1,3 +1,48 @@
+## [23.0.0](https://github.com/sig-nine/era-ui/compare/v22.0.0...v23.0.0) (2026-08-09)
+### ⚠ BREAKING CHANGES
+* **portal:** era owns `Root` for alert-dialog, context-menu, dialog,
+dropdown-menu, link-preview, menubar, sheet and tooltip, where seven of them
+previously re-exported bits-ui's. Behaviour and props are unchanged and `open`
+stays bindable, but anyone importing `Root` for its bits-ui identity — a type
+cast, an `instanceof`-style comparison — is now getting era's wrapper. Content
+opened inside a scoped subtree also now RENDERS with that subtree's axes rather
+than the document's, which is the point, and is a visible change anywhere a
+scope existed and was being silently ignored.
+* **types:** `PartProps<T>` no longer strips `child`. Anything relying on it
+to produce a child-free prop type should use `OwnedPartProps<T>`, which is the
+old definition under a name that says why.
+### Features
+* **nav:** a navigation landmark whose current item announces itself ([9ffb1f2](https://github.com/sig-nine/era-ui/commit/9ffb1f2519b15aa312e6a545eb2462bdf4d9d6a0))
+* **portal:** the five axes cross the portal ([de1b2ba](https://github.com/sig-nine/era-ui/commit/de1b2ba066a87bbe331df600edd78ef716ae935e))
+* **types:** restore bits-ui's `child` on the parts era only restyles ([7659a36](https://github.com/sig-nine/era-ui/commit/7659a3643b466ac915c25a7578b94cf6e680d40a))
+## [22.0.0](https://github.com/sig-nine/era-ui/compare/v21.0.0...v22.0.0) (2026-08-09)
+### ⚠ BREAKING CHANGES
+* **font:** a stack is read AT the element carrying `data-font`, so
+`--era-font-mono` / `-sans` / `-serif` must be re-pointed at or above that
+element. Setting one on a descendant of the axis host now does nothing, where
+before it applied to that subtree. /audit was doing exactly this — it re-pointed
+the stacks on its own <main> while the axis lived on <html>, so the harness had
+been measuring the docs' pinned `monospace` while reporting the shipped stack —
+and now sets them on :root. Nesting `data-font` also genuinely works, which for
+anyone relying on the old source-order behaviour is a visible change.
+Closes the test.fixme in axis-nesting.spec.ts; the suite now has no skips.
+### Features
+* **meter:** a meter can say which band its reading is in ([9119e38](https://github.com/sig-nine/era-ui/commit/9119e38425ca511c0ff9f31a52efdf9f80dd390f))
+### Bug Fixes
+* **font:** the font axis resolves by depth, like every other axis ([a1041bd](https://github.com/sig-nine/era-ui/commit/a1041bdc59a41b9829e5dad42bf727f434e67f7f))
 ## [21.0.0](https://github.com/sig-nine/era-ui/compare/v20.0.0...v21.0.0) (2026-08-09)
 ### ⚠ BREAKING CHANGES

package/dist/dev/audit/audits/off-tier-height.js CHANGED Viewed

@@ -2,12 +2,12 @@ import { TOL, tiers } from './_helpers.js';
 /*
  * Every chrome-bearing control must land on a tier.
  *
- * The tier ladder (xs / xxs / sm / md / lg) is the whole basis of the even-gap and
+ * The tier ladder (icon / pill / chip / control / bar) is the whole basis of the even-gap and
  * concentricity laws: those laws are stated in terms of (h_outer − h_inner)/2, so
  * a control that sits BETWEEN tiers can never nest concentrically in anything —
  * it silently poisons every gap around it. That is exactly how the date segments
  * broke: 21px tall, which is no tier at all, so their 1.5px gap could not match any
- * radius step. Putting them on the sm tier (22px) is what let the identity close.
+ * radius step. Putting them on the chip tier (22px) is what let the identity close.
  *
  * A grep cannot see this. `h-[21px]` would be caught by the hardcoded-px rule, but
  * these segments had NO height class at all — 21px was whatever the line box
@@ -21,6 +21,20 @@ export const offTierHeight = {
     severity: 'warn',
     selector: 'button, input, [role="switch"], [role="checkbox"], [role="radio"], [data-segment]',
     check(el) {
+        // AN UNBOUNDED CONTAINER IS NOT A TIER OBJECT. era has one place where a
+        // <button> is a container rather than a control: an interactive Card, which
+        // renders as <button> or <a> and whose height is its content's. Holding it
+        // to a tier would be asking a card to be 32px tall, and the geometric/optical
+        // padding split in density.css exists precisely because unbounded containers
+        // are NOT sized from the ladder.
+        //
+        // Marked, not inferred. The tempting test — "does its padding match an
+        // optical pad token?" — collides: --era-pad-panel is 5.6px at balanced and
+        // --era-inset-chip is 6px, inside this audit's own 0.5px tolerance. That
+        // would silently exempt a real control from the audit that catches poisoned
+        // gaps, which is the worst direction for this rule to be wrong in.
+        if (el.dataset?.eraUnbounded !== undefined)
+            return null;
         const s = getComputedStyle(el);
         // Chromeless controls (Button's `link` variant is tinted text, no box) have
         // no tier to be on — their height is their line box, by design.

package/dist/dev/audit/audits/wall-is-isotropic.js CHANGED Viewed

@@ -31,11 +31,13 @@ import { TOL, flexChildren, isHorizontalFlex, paintsChrome, tiers } from './_hel
  * compare against, and an unbounded container's padding is optical rather than
  * geometric (see the geometric/optical split in density.css).
  *
- * DELIBERATE ASYMMETRY. Some era chrome is legitimately not isotropic: a pane
- * handle sits its leading side at the text inset while the trailing side keeps
- * the concentric wall. Those opt out with data-era-anisotropic, which is a claim
- * a reviewer can check rather than a silence — the same shape as
- * data-era-continuous on surface/invisible-box.
+ * DELIBERATE ASYMMETRY. Some era chrome is legitimately not isotropic, and it
+ * opts out with data-era-anisotropic rather than by being a shape this rule
+ * happens not to match — the same claim-over-silence design as
+ * data-era-continuous on surface/invisible-box. The date/time field inputs carry
+ * it: --era-field-px is the room where typed TEXT starts, purpose-named and
+ * floored in density.css, so 8px at the sides against a 1px concentric gap is
+ * the intended reading and says so at the call site.
  */
 export const wallIsIsotropic = {
     id: 'layout/wall-is-isotropic',
@@ -105,13 +107,16 @@ export const wallIsIsotropic = {
         //   match when an icon is present. Measuring those against the icon
         //   reports 6-vs-5 on rows that are following the house rule.
         //
-        //   A TEXT FIELD (date/time field and their ranges) walls by
-        //   --era-field-px, which density.css names and floors on purpose: it is
-        //   the room where typed text starts, and it is not the segment box's
-        //   concentric gap. Measuring those reports 8-vs-1 on a deliberate choice.
-        //
         // What is left is the case the law is actually about — chrome holding
         // controls — and it is where both shipped bugs were.
+        //
+        // The OTHER standing exception, a text field walling by --era-field-px,
+        // is not handled here: those four components carry data-era-anisotropic
+        // and are turned away at the top of this function. Verified load-bearing
+        // by disabling this heuristic and confirming they stay silent, which is
+        // the point of declaring it — the exemption survives a change to the
+        // scope rule, and it is a claim at the call site rather than a shape
+        // this function happens not to match.
         const CONTROL = 'button, a[href], input, select, textarea, [role="button"], [role="switch"],' +
             ' [role="checkbox"], [role="radio"], [role="combobox"], [role="tab"], [role="menuitem"]';
         const tallestKid = kids.find((k) => Math.abs(k.getBoundingClientRect().height - tallest) <= TOL);