@aceshooting/lyra-ui 18.1.0 → 18.3.0

package/CHANGELOG.md

@@ -1,5 +1,58 @@
 # Changelog
 
+## 18.3.0
+
+### Minor Changes
+
+- f652e93: Add compact sizing and outlined or quiet appearances to `lr-export-button`, plus a public PNG export
+  method for `lr-heatmap` that captures the painted canvas and frozen label bands.
+- 29e5202: Add an opt-in fit-to-viewport policy to `lr-lightbox`, reusing the image viewer fit vocabulary for landscape and tall images.
+
+## 18.2.0
+
+### Minor Changes
+
+- 3c1e25c: `<lr-map>`: add `legendControlRole` for checkbox legend semantics.
+  
+  Every `legendInteractive` row rendered as a `<button aria-pressed>`, which reads as a set of
+  pressed/unpressed actions rather than a checklist of independent show/hide toggles. The new
+  `legendControlRole: 'button' | 'checkbox'` property (default `'button'`) lets a consumer switch the
+  presentation without changing anything else: under `'checkbox'` the SAME `<button>` element renders
+  `role="checkbox"` and `aria-checked` (both `"true"`/`"false"`, inverted from `hiddenCategories`
+  exactly as `aria-pressed` was) in place of `aria-pressed`. The swatch, the label, the click handler
+  and the platform's own Enter/Space activation are unchanged, so the cancelable
+  `lr-map-legend-toggle` veto, `hiddenCategories` round-tripping, `group` sections and
+  `legendCollapsible` all compose with either role. With `legendControlRole` unset, the rendered
+  legend row is unchanged.
+- 2a25254: Fix `--lr-icon-button-size-scope` being inert for most consumers.
+  
+  18.1.0 introduced `--lr-icon-button-size-scope` as the ancestor-scoped icon-button size
+  input, resolving it as
+  `var(--lr-theme-icon-button-size, var(--lr-icon-button-size-scope, 2.5rem))`. That order
+  made the new token dead on arrival for anyone loading the shipped `design-tokens.css`,
+  which declares `--lr-theme-icon-button-size` on `:root`: a `var()` chain only falls
+  through when the referenced property is unset **everywhere**, not merely shadowed nearer
+  the element, so the theme tier always answered first and the subtree override never
+  resolved. Silently — which is precisely the failure mode the token was added to remove.
+  
+  The chain now reads the scope input first. That is also the correct precedence on its own
+  merits: a subtree override should beat an application-wide default. `--lr-icon-button-size`
+  keeps its element-scoped meaning, the coarse-pointer floor still applies to whichever value
+  wins, and the resolved default is unchanged at `2.5rem`.
+  
+  If you worked around this by declaring `--lr-theme-icon-button-size: initial` at `:root`,
+  that workaround is no longer needed and can be removed.
+  
+  The library's own tests missed this because their fixtures compose only the base token
+  layer and never load `design-tokens.css`. A regression test now declares the theme tier on
+  `:root`, reproducing a real consumer's setup.
+
+### Patch Changes
+
+- 3c1e25c: Document `<lr-map>`'s `legendControlRole` property in the authored `llms/media.md` reference: its
+  `'button' | 'checkbox'` values, the `'button'` default, the `aria-checked` inversion (a hidden
+  category renders unchecked), and when to prefer each role.
+
 ## 18.1.0
 
 ### Minor Changes