@aceshooting/lyra-ui 14.2.0 → 14.3.1

package/llms-full.txt

@@ -6047,6 +6047,11 @@ box no matter what tier or override is in play.
   are resolved onto the focused internal control through `ariaDescribedByElements`; external
   `aria-labelledby` is not copied across the shadow boundary.
 - Host `aria-haspopup` and `aria-expanded` values are forwarded to the internal semantic control.
+  For toggle buttons, host `aria-pressed="true|false|mixed"` reaches the focused native button.
+  Navigation can use `aria-current="page|step|location|date|time|true|false"`. Both states update
+  reactively, including native `ariaPressed`/`ariaCurrent` property assignments, attribute removal
+  and `href` changes. Empty or unsupported tokens are omitted. The native button/link role remains
+  unchanged: use pressed state for button toggles and current state for navigation links.
   For host `aria-controls`, targets in the host's own root are resolved through the reflected
   element-reference API so a popup relationship survives the component's shadow boundary; browsers
   with that API expose the relationship through `ariaControlsElements` and intentionally serialize
@@ -10654,6 +10659,10 @@ cell: (row) => unknown }` —
   the two consequences of the fixed algorithm worth knowing before opting in
 - `sortKey: string = ''` (attribute `sort-key`)
 - `sortDir: 'asc'|'desc' = 'asc'` (attribute `sort-dir`)
+- `sortIndicators: TableSortIndicators = 'active'` (attribute `sort-indicators`) — `'all'` adds a
+  muted bidirectional indicator to each inactive sortable header, reserving the same space as the
+  active chevron. The default retains only the active column's indicator. This presentation does
+  not change keyboard interaction, client/server sorting, or `aria-sort="none"` on inactive columns.
 - `sortMode: 'client'|'server' = 'client'` (attribute `sort-mode`, reflected) — mirrors
   `paginationMode`'s identical split. `'client'` (the default) orders `rows` in the browser from
   `sortKey`/`sortDir` and the active column's `sortValue`; `'server'` renders `rows` exactly as
@@ -10824,8 +10833,9 @@ slot-replaceable: it reports a configuration problem (`noColumnsHeading`), not "
 nothing", and one slot covering all three would collapse that distinction. Everything else comes
 from `columns`/`rows`.
 
-**CSS parts:** `base`, `table`, `caption`, `head`, `header-cell`, `row`, `cell`, `more-button`, `sort-icon` (a
-chevron indicator shown on the active sortable header, rotated per `sortDir`), `reveal-columns-button`
+**CSS parts:** `base`, `table`, `caption`, `head`, `header-cell`, `row`, `cell`, `more-button`, `sort-icon`
+(each sort indicator), `sort-icon-active` (the active chevron, rotated per `sortDir`),
+`sort-icon-inactive` (the muted bidirectional indicator under `sort-indicators="all"`), `reveal-columns-button`
 (shown when priority columns are hidden or when a narrow allocation is currently force-visible),
 `foot` (the `<tfoot>`, only rendered when at least one
 column defines `footer`), `footer-row`, `footer-cell`, `row-total-cell` (each body row's trailing
@@ -10895,7 +10905,8 @@ or structural-pseudo-class selector and does not affect group, expanded, hover,
 showing through the sticky header while it scrolls.
 Same shape and rationale as `--lr-table-row-selected-bg`: inline `var()` fallbacks, not on `:host`,
 because `::part(header-cell)[aria-sort]` is invalid CSS. The `sort-icon` part styles only the
-chevron; these tokens style the header cell itself.
+indicator; these tokens style the header cell itself. Use `::part(sort-icon-inactive)` and
+`::part(sort-icon-active)` to style the two indicator states without private selectors.
 `--lr-table-sticky-offset` (default `0`) is measured and written inline per column by the component
 so multiple `sticky` columns stack instead of overlapping; it is a read-out, not a knob you set.
 `--lr-table-heat-t` is likewise component-written (each `[data-heat]` cell's position on the ramp).
@@ -17456,6 +17467,42 @@ findable `hidden="until-found"` closed-state gate.
 The Details icon wrapper also carries Shoelace's `summary-icon` alias, so either part name styles
 the same node. `header-actions` is the wrapper around the `header-actions` slot.
 
+For rich independent actions, reserve a useful basis on `header-actions` so the complete action
+group wraps onto another row before its checkbox label becomes too narrow. The header already
+wraps; its summary belongs to a private native-details flex item, so setting `flex` on
+`::part(summary)` does not control that item's allocation. This recipe uses public parts and
+ordinary light-DOM layout:
+
+```html
+<style>
+  lr-details.responsive-actions::part(header-actions) {
+    flex: 1 1 12rem;
+    min-inline-size: min(100%, 12rem);
+    padding: var(--lr-space-xs);
+    box-sizing: border-box;
+  }
+  .details-action-group {
+    display: flex;
+    flex-wrap: wrap;
+    align-items: center;
+    gap: var(--lr-space-s);
+    min-inline-size: 0;
+  }
+  .details-action-group lr-checkbox { flex: 1 1 auto; min-inline-size: 0; }
+</style>
+<lr-details class="responsive-actions" summary="Settings">
+  <span slot="header-actions" class="details-action-group">
+    <lr-checkbox size="s">Show distribution details</lr-checkbox>
+    <lr-badge>Live</lr-badge>
+  </span>
+  Distribution settings.
+</lr-details>
+```
+
+Import the granular details, checkbox and badge registration entries. Adjust the `12rem` basis
+for the actual labels. Logical sizing supports RTL and narrower allocations; the checkbox remains
+independently focusable and operable when the summary is disabled.
+
 **Themeable custom properties:** accordion item exposes `--lr-accordion-item-spacing` (default
 `var(--lr-form-control-padding-inline)`), `--lr-accordion-item-show-duration` and
 `--lr-accordion-item-hide-duration` (both default `var(--lr-duration-base)`), and
@@ -20386,6 +20433,11 @@ consumer-supplied `lr-menu` in the default slot becomes that contained engine in
 wrapped in another menu. This supports both Web Awesome's direct-item shape and Shoelace's
 consumer-menu shape.
 
+The inner menu list owns scrolling within the popup's height limit, keeping a consumer menu's
+header and footer visible. The outer `popup` and `content` parts allow overflow so nested submenus
+remain clickable outside the parent menu in every supported browser. This works with either
+submenu authoring shape, with or without `hoist` or an arrow; no overflow override is required.
+
 An open lr-dropdown repositions when its effective host or inherited text direction changes,
 preserving open state without emitting lifecycle events.
 
@@ -23865,16 +23917,36 @@ intensity?: LyraMapHeatmapZoomValue; opacity?: number }`, where `LyraMapHeatmapZ
   defaults to 5 CSS pixels and `strokeWidth` to 0; both clamp to `[0, 200]`. `strokeColor` overrides
   the outline only, with the layer's flat color as fallback. Dropping options restores defaults.
 
+  `radius` also accepts `LyraMapPointRadiusOptions { field, stops, interpolation?, fallback? }`
+  for **numeric** feature-driven sizes. `field` is independent of the category field. The first 32
+  pairs are inspected and finite `[value, radius]` pairs are sorted ascending; duplicate thresholds are first-wins and
+  radii clamp to `[0, 200]`. `interpolation` defaults to `'step'`: below the first threshold use
+  its radius, and each threshold is inclusive. `'linear'` interpolates between adjacent stops and
+  clamps outside the domain. One usable stop is a constant for numeric features. Missing, null,
+  non-numeric and non-finite feature values use `fallback` (default 5, clamped to `[0, 200]`), as
+  do an empty field, unusable stops or a linear domain that cannot retain distinct finite intervals.
+  Invalid interpolation values use step. These options style individual/unclustered points;
+  cluster-count radii remain independent. Switching back to a number or removing the radius
+  scale restores the fixed radius without recreating the source.
+
   `point.icons` maps exact category values to `LyraMapPointIcon { value: string; path: string;
-  viewBox?: readonly [number, number, number, number] }`. `iconField` defaults to `field`.
-  Each icon is a **filled SVG path string**, not SVG markup or a URL. Copy an icon's path data,
+  viewBox?: readonly [number, number, number, number]; mode?: LyraMapPointIconMode;
+  strokeWidth?: number; lineCap?: LyraMapPointIconLineCap; lineJoin?: LyraMapPointIconLineJoin }`.
+  `iconField` defaults to `field`. Each icon is **SVG path data**, not SVG markup or a URL. Copy an icon's path data,
   combine filled subpaths in that string, and supply its `[minX, minY, width, height]` viewBox
-  (default `[0, 0, 24, 24]`). Stroke-only drawings must first be converted to filled outlines.
+  (default `[0, 0, 24, 24]`). `mode` defaults to `'fill'`; `'stroke'` draws open outline paths,
+  and `'fill-stroke'` paints both. `strokeWidth` uses **viewBox units** (default 2, clamped to
+  `[0, 200]`; zero omits the stroke), so it scales with the icon. `lineCap` accepts `'butt'`,
+  `'round'`, or `'square'`; `lineJoin` accepts `'miter'`, `'round'`, or `'bevel'`. Both default
+  to round; miter joins retain a limit of 10. Invalid modes/caps/joins restore their defaults,
+  and a non-finite stroke width restores 2. Keep padding inside the viewBox for strokes at its
+  edges, which are clipped to the fixed atlas square. These are icon-path options;
+  `point.strokeWidth` and `point.strokeColor` continue to style the surrounding circle only.
   The first 32 entries are inspected, valid duplicates are first-wins, path data is capped at
   8192 characters, and viewBox coordinates must be finite within ±10000 with dimensions at least
   0.001. Invalid paths are ignored; markup, external references and event handlers cannot execute.
   Rasterization is synchronous and local, with no fetch or HTML/SVG document insertion.
-  `iconColor` accepts CSS variables and defaults to the tone's contrasting foreground; `iconSize`
+  `iconColor` supplies both fill and stroke ink, accepts CSS variables and defaults to the tone's contrasting foreground; `iconSize`
   is the displayed bounding square in CSS pixels (default 16, clamped to `[1, 200]`). The fixed
   64px raster preserves the viewBox aspect ratio. Unknown categories, invalid icons and partial
   peers lacking image-atlas methods retain their colored circles. No sprite or glyph URL is needed.
@@ -23894,11 +23966,14 @@ intensity?: LyraMapHeatmapZoomValue; opacity?: number }`, where `LyraMapHeatmapZ
   map.dataLayers = [{
     sourceId: 'places', geojson: locations, cluster: {},
     point: {
-      field: 'category', radius: 12, strokeWidth: 1,
+      field: 'category',
+      radius: { field: 'visits', stops: [[0, 10], [10, 12], [50, 14], [100, 16]], fallback: 10 },
+      strokeWidth: 1,
       colors: [['home', 'var(--lr-color-brand)'], ['work', 'var(--lr-color-success)']],
       icons: [
         { value: 'home', path: 'M2 12L12 2L22 12V22H2Z' },
-        { value: 'work', path: 'M8 2H16V6H22V22H2V6H8Z' },
+        { value: 'work', path: 'M8 6V3H16V6M3 6H21V21H3ZM3 11H21',
+          mode: 'stroke', strokeWidth: 1.75, lineCap: 'round', lineJoin: 'round' },
       ],
       iconSize: 14,
     },
@@ -23962,7 +24037,9 @@ payload beside the map.
 
 **Authoring types:** `LyraMapLegendEntry`, `LyraMapLegendPattern`, `LyraMapLegendProjection`, `LyraMapChoroplethLayer`,
 `LyraMapGeoJsonDataLayer`, `LyraMapDataLayerKind`, `LyraMapClusterOptions`, `LyraMapHeatmapOptions`,
-`LyraMapHeatmapZoomValue`, `LyraMapLineOptions`, `LyraMapPointOptions`, `LyraMapPointIcon`, `LyraMapMarker`, `LyraMapMarkerActivationDetail`,
+`LyraMapHeatmapZoomValue`, `LyraMapLineOptions`, `LyraMapPointOptions`, `LyraMapPointRadiusOptions`,
+`LyraMapPointRadiusInterpolation`, `LyraMapPointIcon`, `LyraMapPointIconMode`,
+`LyraMapPointIconLineCap`, `LyraMapPointIconLineJoin`, `LyraMapMarker`, `LyraMapMarkerActivationDetail`,
 `LyraMapMarkerActivationSource`, `LyraMapStyleSpecification`, and `LyraMapInstance`.
 The former `LegendEntry`, `ChoroplethLayer`, `GeoJsonDataLayer`, and `MapMarker` names are removed
 in v9 rather than retained as aliases.
@@ -24007,6 +24084,16 @@ when `legend` and `legendGradient` are both empty.
 `legend-hi`, `legend-limit`, `marker`, `popup`,
 `popup-content`, `popup-close-button`, `attribution`, `attribution-toggle`, `navigation`,
 `zoom-in`, `zoom-out`, `compass`, `scale`, `error`.
+The compact attribution summary has a decorative, current-color information glyph and retains
+MapLibre's accessible name, keyboard/touch disclosure behavior and attribution links. To make
+only this control compact, scope the shared target-size token to its public wrapper:
+
+```css
+lr-map::part(attribution) { --lr-icon-button-size: var(--lr-size-24px); }
+```
+
+Keep that target at least 24px in both axes. This leaves navigation controls at their existing size.
+
 `legend` is a localized `role="group"` containing a real list associated to the map canvas with
 `aria-describedby`; each entry is a `listitem`, decorative swatches are inert/accessibility-hidden,
 and the overlay is bounded to the map allocation with scrolling and long-label wrapping.
@@ -24025,6 +24112,9 @@ and use `addControl(new NavigationControl(), 'bottom-right')` and
 shadow-root modification is needed: navigation buttons, compass glyph, scale bar and control
 corners are styled with Lyra tokens. The corners follow inline start/end under RTL. The legend
 reserves vertical room for these controls and attribution, including after resize or removal.
+Attribution also reserves legend space when it is the only control. Opposing occupied corners
+share the available width, so expanded attribution wraps without covering a scale or navigation
+control on the other side; controls stay aligned to their logical edge in both text directions.
 Navigation exposes `navigation`, `zoom-in`, `zoom-out`, and `compass` parts; the scale exposes `scale`.
 Button names update through `zoomIn`, `zoomOut`, and `mapResetNorth` locale strings. MapLibre retains
 keyboard activation, compass rotation, zoom limits, scale units and viewport updates. No controls
@@ -26427,12 +26517,16 @@ These named interfaces and helper signatures are available to typed integrations
     readonly value: string;
     readonly path: string;
     readonly viewBox?: readonly [number, number, number, number];
+    readonly mode?: LyraMapPointIconMode;
+    readonly strokeWidth?: number;
+    readonly lineCap?: LyraMapPointIconLineCap;
+    readonly lineJoin?: LyraMapPointIconLineJoin;
   }`
   Import: `@aceshooting/lyra-ui/components/media/map/map.class.js`.
   `LyraMapPointOptions {
     readonly field?: string;
     readonly colors?: readonly (readonly [string, string])[];
-    readonly radius?: number;
+    readonly radius?: number | LyraMapPointRadiusOptions;
     readonly strokeWidth?: number;
     readonly strokeColor?: string;
     readonly iconField?: string;
@@ -26441,6 +26535,17 @@ These named interfaces and helper signatures are available to typed integrations
     readonly iconSize?: number;
   }`
   Import: `@aceshooting/lyra-ui/components/media/map/map.class.js`.
+  `LyraMapPointRadiusOptions {
+    readonly field: string;
+    readonly stops: readonly (readonly [number, number])[];
+    readonly interpolation?: LyraMapPointRadiusInterpolation;
+    readonly fallback?: number;
+  }`
+  `LyraMapPointRadiusInterpolation = 'step' | 'linear'`;
+  `LyraMapPointIconMode = 'fill' | 'stroke' | 'fill-stroke'`;
+  `LyraMapPointIconLineCap = 'butt' | 'round' | 'square'`;
+  `LyraMapPointIconLineJoin = 'miter' | 'round' | 'bevel'`.
+  Import: `@aceshooting/lyra-ui/components/media/map/map.class.js`.
   `LyraMapInstance {
     getCanvas(): HTMLCanvasElement;
     getCenter(): {
@@ -26699,6 +26804,28 @@ structured points retain their y-value formatting.
   would clip. Its pressed state follows `hiddenDatasets` whenever that controlled snapshot is
   defined, otherwise the effective dataset's declarative `hidden` value before Chart.js is ready
   and across chart type/plugin rebuilds.
+- `legendMode: LyraChartLegendMode = 'dataset'` (attribute `legend-mode`) — `dataset` preserves
+  dataset toggles. `datum` shows one category toggle per slice in pie, doughnut and polar-area
+  charts; other types retain dataset legends. Category names use source labels with localized
+  numbered fallbacks. Colors and values come from the first dataset. With multiple datasets/rings,
+  a category toggle hides that source index in every ring, matching Chart.js category visibility.
+- `hiddenDatums: readonly number[] = []` (attribute: false) — clone-owned hidden source category
+  indexes for radial charts. `[]` restores all categories. Invalid, duplicate and out-of-range
+  indexes are ignored when applied or emitted. Programmatic changes are silent; accepted datum
+  legend toggles write the complete next snapshot. Data and type replacements, reconnection and
+  sampling retain source-index meaning. This state is independent of `hiddenDatasets`; hiding a
+  whole dataset continues to hide its ring. Accessible data and CSV export retain hidden values.
+- `legendDisplay: LyraChartLegendDisplay = 'auto'` (attribute `legend-display`) — `auto` preserves
+  the existing label with optional legend formatting. `label` always shows labels alone, even when
+  `formatter`/`valueFormatter` supplies values for tooltips or axes. `value` appends the formatted
+  numeric value. `percentage` appends a locale-formatted share independently of these callbacks:
+  the denominator is the sum of absolute represented legend values, including hidden entries.
+  Dataset entries use sampled sums; category entries use the first dataset's represented values.
+  Zero totals give 0%. These options affect the DOM legend; tooltip/axis/table formatting is unchanged.
+  Simplified pie/doughnut datasets with magnitudes above `Number.MAX_SAFE_INTEGER` are uniformly
+  rescaled for finite canvas geometry. Lyra tooltips, data labels, legends, events and CSV retain
+  original values; direct Chart.js callbacks see the rescaled peer data. Explicit `config.data`
+  remains the unmodified full-fidelity escape hatch.
 - `legendPosition: LyraChartLegendPosition = 'top'` (attribute `legend-position`) — accepts the
   Chart.js `left|top|right|bottom|center|chartArea|{ [scaleId]: number }` positions plus logical
   `start`/`end`; the additive `auto` chooses right above 480px and bottom below that allocation
@@ -26882,6 +27009,22 @@ family-wide handling; `lr-point-click` remains as a compatibility event. Also
 `{ datasetIndex: number, visible: boolean, hiddenDatasets: readonly number[] }`; the latter is the
 complete, sorted, valid next snapshot. Call `preventDefault()` on the proposal to veto the toggle;
 then no property change or commit event occurs.
+Category toggles use a separate pair, `lr-before-datum-visibility-change` (cancelable proposal) and
+`lr-datum-visibility-change` (accepted commit), carrying
+`{ index: number, visible: boolean, hiddenDatums: readonly number[] }`. Both details and their
+complete, sorted index snapshots are frozen. `index` is the source category index, including when
+the displayed data is sampled; it applies across all rings. Programmatic assignments emit neither
+pair. `preventDefault()` leaves both controlled state and the chart unchanged.
+
+```html
+<lr-doughnut-chart
+  legend-mode="datum"
+  legend-display="label"
+  .labels=${['A', 'B', 'C']}
+  .datasets=${[{ label: 'Distribution', data: [5, 3, 2] }]}
+  .hiddenDatums=${[]}
+></lr-doughnut-chart>
+```
 
 **Slots:** default — one optional `<script type="application/json">` Chart.js configuration;
 `data-table` — an optional consumer-provided complete, paginated, or virtualized accessible table
@@ -26899,8 +27042,8 @@ another application-owned presentation. Explicit `config.data` is the deliberate
 Chart.js escape hatch and is not rewritten by the simplified-surface sampler.
 
 **CSS parts:** `base`, `plot` (the fixed-height canvas/overlay region), `canvas`, `legend` (the
-wrapping DOM legend), `legend-item` (a dataset-visibility button), `legend-item-hidden` (added to
-that button while its dataset is hidden), `legend-swatch`,
+wrapping DOM legend), `legend-item` (a dataset/category visibility button), `legend-item-hidden`
+(added while the dataset/category is hidden), `legend-swatch`,
 `reset-zoom-button`, `description`, `notices` (wrapper for nonfatal feature warnings and
 bounded-alternative truncation notices), `data-table`, `data-table-toggle` (the `dataTableToggle` disclosure button), `data-truncation` (the bounded-alternative
 notice), `feature-warning` (a nonfatal missing optional-feature warning), `center` (the
@@ -27358,7 +27501,8 @@ and behavior there. **See `llms/components/lr-chart.md` for the details, code ex
 of every entry in these lists.**
 
 **Properties:** `description`, `grid`, `axes`, `compact`, `indexAxis` (`index-axis`), `label`, `hiddenDatasets`, `legendPosition`
-(`legend-position`), `max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
+(`legend-position`), `hiddenDatums`, `legendMode` (`legend-mode`), `legendDisplay` (`legend-display`),
+`max`, `min`, `plugins`, `scaleType` (`scale-type`), `annotations`,
 `stacked`, `withoutAnimation` (`without-animation`),
 `withoutLegend` (`without-legend`), `withoutTooltip` (`without-tooltip`), `xLabel` (`x-label`),
 `yLabel` (`y-label`), plus additive `labels`, `datasets`, `valueFormatter`, `formatter`, `area`, `zoom`,
@@ -27374,6 +27518,8 @@ of every entry in these lists.**
 index, label, value }`), `lr-before-legend-visibility-change` (cancelable), and
 `lr-legend-visibility-change` (commit; both legend events carry `datasetIndex`, `visible`, and the
 complete `hiddenDatasets` snapshot).
+Radial category legends additionally emit `lr-before-datum-visibility-change` (cancelable) and
+`lr-datum-visibility-change`, carrying `index`, `visible` and the frozen `hiddenDatums` snapshot.
 
 **Slots:** default JSON configuration script, `data-table`, `center`.
 
@@ -27443,7 +27589,8 @@ Bins `values` into `bins` equal-width buckets and renders as a bar chart (extend
   normalized `bins`), and `type` always reads back `'bar'` regardless of any assignment. This
   specialist owns its controller because a non-bar type would contradict the derived distribution.
 - All other `LyraChart` properties are inherited and usable: `description`, `grid`, `axes`, `compact`, `indexAxis`
-  (`index-axis`), `hiddenDatasets`, `legendPosition` (`legend-position`), `max`, `min`, `plugins`,
+  (`index-axis`), `hiddenDatasets`, `hiddenDatums`, `legendPosition` (`legend-position`),
+  `legendMode` (`legend-mode`), `legendDisplay` (`legend-display`), `max`, `min`, `plugins`,
   `withoutAnimation` (`without-animation`), `withoutLegend` (`without-legend`), `withoutTooltip`
   (`without-tooltip`), `valueFormatter`, `formatter`, `area`, `zoom`, `config`, `height`, `xLabel` (`x-label`),
   `yLabel` (`y-label`), `y2Label` (`y2-label`), `beginAtZero` (`begin-at-zero`),
@@ -27455,9 +27602,12 @@ maxSamples?)` appends finite raw samples and optionally retains only the newest
 `appendData()` remains a working compatibility adapter (no longer deprecated); prefer
 `appendSamples()` for new code.
 
-**Events:** `lr-zoom`, `lr-datum-activate`, `lr-point-click`, `lr-before-legend-visibility-change` (cancelable), and
+**Events:** `lr-zoom`, `lr-datum-activate`, `lr-point-click`, `lr-before-datum-visibility-change`
+(cancelable), `lr-datum-visibility-change`, `lr-before-legend-visibility-change` (cancelable), and
 `lr-legend-visibility-change` — inherited; `lr-point-click`'s `index` is the bucket index and
 `label` the generated bucket range string (`"lo–hi"`, both bounds at one decimal place).
+The inherited datum-visibility events apply only to radial controllers; the histogram keeps its
+bar controller and dataset legend even with `legend-mode="datum"`.
 
 **Slots:** default JSON configuration script, `data-table`, `center`.
 
@@ -27774,6 +27924,14 @@ These named interfaces and helper signatures are available to typed integrations
     readonly visible: boolean;
     readonly hiddenDatasets: readonly number[];
   }`
+  Import: `@aceshooting/lyra-ui/components/charts/chart/chart.class.js`.
+  `LyraChartDatumVisibilityChangeDetail {
+    readonly index: number;
+    readonly visible: boolean;
+    readonly hiddenDatums: readonly number[];
+  }`
+  `LyraChartLegendMode = 'dataset' | 'datum'`
+  `LyraChartLegendDisplay = 'auto' | 'label' | 'value' | 'percentage'`
 
 - **`components-charts-chart-chart-loader-contracts`** — Supporting data types and helpers for this component family.
   Import: `@aceshooting/lyra-ui/components/charts/chart/chart-feature-loader.js`.
@@ -27910,6 +28068,8 @@ These named interfaces and helper signatures are available to typed integrations
     };
     isDatasetVisible(index: number): boolean;
     setDatasetVisibility(index: number, visible: boolean): void;
+    getDataVisibility?(index: number): boolean;
+    toggleDataVisibility?(index: number): void;
   }`
   Import: `@aceshooting/lyra-ui/components/charts/chart/chart.class.js`.
   `LyraChartPlugin {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aceshooting/lyra-ui",
-  "version": "14.2.0",
+  "version": "14.3.1",
   "description": "Free, independent Lit web components: an open-source alternative to Shoelace and Web Awesome with accessible forms, dashboards, charts, and agent UI.",
   "keywords": [
     "web-components",
@@ -2408,7 +2408,7 @@
     "@types/mocha": "^10.0.10",
     "@types/papaparse": "^5.5.2",
     "@types/qrcode": "^1.5.6",
-    "@types/react": "^19.2.18",
+    "@types/react": "^19.3.0",
     "@web/dev-server-esbuild": "^2.0.0",
     "@web/test-runner": "^1.0.0",
     "@web/test-runner-commands": "^1.0.1",
@@ -2430,13 +2430,13 @@
     "istanbul-lib-coverage": "^3.2.2",
     "istanbul-lib-report": "^3.0.1",
     "istanbul-reports": "^3.2.0",
-    "jszip": "^3.10.1",
+    "jszip": "^3.10.2",
     "katex": "^0.18.7",
-    "libphonenumber-js": "^1.13.12",
+    "libphonenumber-js": "^1.13.13",
     "mammoth": "^1.12.2",
-    "maplibre-gl": "^6.7.0",
-    "marked": "^18.0.11",
-    "oxc-parser": "^0.148.0",
+    "maplibre-gl": "^6.9.0",
+    "marked": "^18.0.12",
+    "oxc-parser": "^0.149.0",
     "papaparse": "^5.7.0",
     "pdfjs-dist": "^6.3.289",
     "pixelmatch": "^7.2.0",
@@ -2444,7 +2444,7 @@
     "pngjs": "^7.0.0",
     "postal-mime": "^3.0.0",
     "qrcode": "^1.5.4",
-    "react": "^19.2.8",
+    "react": "^19.3.0",
     "shiki": "^4.4.3",
     "svelte": "^5.57.0",
     "typescript": "^7.0.2",