@aceshooting/lyra-ui 12.1.1 → 12.1.2

package/llms/components/lr-geojson-viewer.md

@@ -48,7 +48,8 @@ text, independent of whether the optional map peer is available.
 
 **Events:**
 
-- `lr-render-error` — `detail: { error }` — fetch, parse, or shape-validation failure.
+- `lr-render-error` — `detail: { error }` — fetch, parse, shape-validation, or missing-map capability
+  failure. A missing optional MapLibre peer also keeps the serialized metadata fallback visible.
 - `lr-search-change` — `detail: { query: string; matchCount: number; matchCountExact: boolean; activeIndex: number }` — fired
   whenever serialized-metadata search state changes.
 - `lr-anchor-result` — `detail: { found: boolean }` — fired after an `anchor` assignment or

package/llms/components/lr-map.md

@@ -136,7 +136,7 @@ heatmap?: LyraMapHeatmapOptions; cluster?: LyraMapClusterOptions }`. `sourceId`
   its private source/layers removed, and a genuinely new `sourceId` gets new resources — nothing
   leaks on removal, style change, or disconnect.
 
-  `cluster` and `kind` (both new in 12.1.0) opt one entry out of that three-layer geometry split.
+  `cluster` and `kind` (both new in 12.0.0) opt one entry out of that three-layer geometry split.
   **Both are strictly additive: an entry that sets neither renders exactly what it rendered before,
   down to the layer ids and the point layer's filter.**
 

package/llms-full.txt

@@ -5114,7 +5114,7 @@ Text field + calendar popover, **form-associated** via the shared `FormAssociate
 **Properties (44):**
 
 - `appearance: 'filled'|'outlined'|'filled-outlined' = 'outlined'` (reflected)
-- `appliedPreset: LyraDateRangePreset | undefined` (read-only, new in 12.1.0) — the `presets` entry
+- `appliedPreset: LyraDateRangePreset | undefined` (read-only, new in 12.0.0) — the `presets` entry
   whose button produced the current `value`, or `undefined` when the value was picked on the
   calendar, typed into the field, cleared, or reset. Read it inside your own `change`/`input`
   handler; it is updated before those events are relayed, so a handler observes the preset that
@@ -16424,7 +16424,7 @@ no-op if already open),
 cycling) at the ends; the active row is scrolled into view. Enter selects. Hovering a non-disabled
 row also makes it active.
 
-**Events:** `lr-open`, `lr-close` (both `detail: undefined`, cancelable — fired before the
+**Events:** `lr-open`, `lr-close` (both `detail: null`, cancelable — fired before the
 mutation, `preventDefault()` keeps the palette in its current open state), `lr-select`
 (`detail: { command }`, fired before the command's own `onSelect` runs and before the palette
 closes), and no-detail `focus`/`blur` events re-dispatched from the host whenever the search input
@@ -16922,7 +16922,7 @@ value therefore stays inside a 320px LTR or RTL bar, with the chip's own label e
 overflow ownership rather than widening the page.
 
 Each edit exposes one filter-bar `lr-input` carrying a detached, deeply frozen snapshot of the
-complete value object, plus the `filterId` that changed and (new in 12.1.0) `appliedPreset` — see
+complete value object, plus the `filterId` that changed and (new in 12.0.0) `appliedPreset` — see
 "Date-range quick ranges" below. A built-in or
 custom control's own `lr-input`/`lr-change` aliases stay inside the wrapper so their incompatible
 detail shapes cannot escape as duplicate bar events; native-style `input`/`change` events from the
@@ -16975,7 +16975,7 @@ text the user typed, not a truncated or normalized form.
 
 ### Date-range quick ranges
 
-A `'date-range'` definition also accepts `presets?: readonly LyraDateRangePreset[]` (new in 12.1.0),
+A `'date-range'` definition also accepts `presets?: readonly LyraDateRangePreset[]` (new in 12.0.0),
 forwarded to its composed `<lr-date-input>` exactly like `min`/`max`, so the quick-range row
 ("Today", "Last 7 days", "All time") renders inside that filter's own calendar popover. Entries are
 `LyraDateRangePreset { label, start?, end? }` with ISO `YYYY-MM-DD` bounds; an omitted bound is open
@@ -22609,7 +22609,7 @@ heatmap?: LyraMapHeatmapOptions; cluster?: LyraMapClusterOptions }`. `sourceId`
   its private source/layers removed, and a genuinely new `sourceId` gets new resources — nothing
   leaks on removal, style change, or disconnect.
 
-  `cluster` and `kind` (both new in 12.1.0) opt one entry out of that three-layer geometry split.
+  `cluster` and `kind` (both new in 12.0.0) opt one entry out of that three-layer geometry split.
   **Both are strictly additive: an entry that sets neither renders exactly what it rendered before,
   down to the layer ids and the point layer's filter.**
 
@@ -26491,9 +26491,9 @@ matches, the anchor isn't `region`, or the format isn't currently `image`.
 - `lr-download` — `detail: { src, filename }` — fired when the generic-download fallback's link is
   activated. The browser download itself needs no JS (a plain `<a download>` handles it); this is
   purely for a host that wants to observe/log the download.
-- `lr-render-error` — `detail: { error }` — fired when this component's own `text/*`/
-  `application/json` `fetch(src)` fails (network error or non-2xx response). Distinct from
-  `status="error"`, which is entirely host-driven.
+- `lr-render-error` — `detail: { error }` — fired when this component rejects an unsafe text/JSON
+  URL or when its own `text/*`/`application/json` `fetch(src)` fails (network error or non-2xx
+  response). Distinct from `status="error"`, which is entirely host-driven.
 - `lr-highlight-activate` — `detail: { highlightId }` — a region highlight was clicked or activated via
   Enter/Space (image format only).
 
@@ -26603,11 +26603,12 @@ document-level assertive sink.
   for text/image sinks and `mailto:` is accepted for navigation anchors elsewhere in the library — a
   `src="data:..."` document renders/fetches fine but falls back to no download affordance in the
   generic state, and a `mailto:` names no retrievable bytes so it cannot be a download target at all.
-- A `src` that fails its sink's URL-safety check does **not** raise `lr-render-error` — that event is
-  reserved for a `fetch()` that was actually attempted and failed at the network layer; an unsafe/
-  malformed `src` is silently treated as unusable instead (a rendered `[part="error"]` message for
-  text, a silent fallback for image/download — and on the image path that fallback is the download
-  fallback directly, so an `unsupported` slot the host supplied is bypassed).
+- A `src` that fails its sink's URL-safety check raises `lr-render-error` for the text/JSON path,
+  with the localized URL-rejection error; the event is also raised when an allowed `fetch()` fails
+  at the network layer. An unsafe/malformed image or download `src` is instead treated as unusable
+  without an event (a silent image fallback or omitted download link — and on the image path that
+  fallback is the download fallback directly, so an `unsupported` slot the host supplied is
+  bypassed).
 
 ---
 
@@ -26774,8 +26775,9 @@ exactly one `lr-anchor-result` with `{ found: false }`.
 
 Fetches a `.docx` Word document as an `ArrayBuffer`, converts it to semantic HTML with the optional
 `mammoth` peer, sanitizes that HTML through the optional `dompurify` peer, and renders the result.
-Mammoth preserves document structure such as headings, paragraphs, lists, tables, and images; it is
-not intended to reproduce pixel-exact Word page layout. There is no unsanitized rendering escape
+Mammoth preserves document structure such as headings, paragraphs, lists, tables, and validated
+inline raster images; it is not intended to reproduce pixel-exact Word page layout. There is no
+unsanitized rendering escape
 hatch: if `dompurify` is unavailable, rendering is blocked even when Mammoth converted successfully.
 
 Every rendered heading's slug (the same GitHub-slugger-style algorithm `<lr-markdown>` uses) is
@@ -28298,7 +28300,8 @@ text, independent of whether the optional map peer is available.
 
 **Events:**
 
-- `lr-render-error` — `detail: { error }` — fetch, parse, or shape-validation failure.
+- `lr-render-error` — `detail: { error }` — fetch, parse, shape-validation, or missing-map capability
+  failure. A missing optional MapLibre peer also keeps the serialized metadata fallback visible.
 - `lr-search-change` — `detail: { query: string; matchCount: number; matchCountExact: boolean; activeIndex: number }` — fired
   whenever serialized-metadata search state changes.
 - `lr-anchor-result` — `detail: { found: boolean }` — fired after an `anchor` assignment or

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aceshooting/lyra-ui",
-  "version": "12.1.1",
+  "version": "12.1.2",
   "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",

package/vscode-html-data.json

@@ -23089,7 +23089,7 @@
           "name": "label",
           "description": {
             "kind": "markdown",
-            "value": "Header text used when `label-plural` isn't set, e.g. `\"Sources\"`. Omitting it falls back to\na localized default; an explicit empty string clears it (still overridden by\n`label-plural` when that's set).\n\nType: `string | undefined`"
+            "value": "Header text used when `label-plural` isn't set, e.g. `\"Sources\"`. Omitting it falls back to\na localized default; an explicit empty string uses that localized accessible fallback so the\ndisclosure button always has a name (still overridden by `label-plural` when that's set).\n\nType: `string | undefined`"
           }
         },
         {

package/web-types.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/web-types",
   "name": "@aceshooting/lyra-ui",
-  "version": "12.1.1",
+  "version": "12.1.2",
   "description-markup": "markdown",
   "contributions": {
     "html": {
@@ -17400,7 +17400,7 @@
               },
               {
                 "name": "lr-render-error",
-                "description": "`detail: { error }` — fired when this component's own `text/*`/`application/json` `fetch(src)` fails. Distinct from `status=\"error\"`, which is entirely host-driven (see the class doc).",
+                "description": "`detail: { error }` — fired when this component rejects an unsafe text/JSON URL or when its own `text/*`/`application/json` `fetch(src)` fails. Distinct from `status=\"error\"`, which is entirely host-driven (see the class doc).",
                 "type": "CustomEvent<{ error: unknown }>"
               }
             ]
@@ -23626,7 +23626,7 @@
               },
               {
                 "name": "lr-render-error",
-                "description": "Fetch, parse, or shape-validation failure. `detail: { error }`.",
+                "description": "Fetch, parse, shape-validation, or missing-map-capability failure. `detail: { error }`. A missing optional MapLibre peer leaves the serialized metadata fallback visible while reporting the degraded map capability.",
                 "type": "CustomEvent<{ error: unknown }>"
               },
               {
@@ -23737,7 +23737,7 @@
               },
               {
                 "name": "lr-render-error",
-                "description": "Fetch, parse, or shape-validation failure. `detail: { error }`.",
+                "description": "Fetch, parse, shape-validation, or missing-map-capability failure. `detail: { error }`. A missing optional MapLibre peer leaves the serialized metadata fallback visible while reporting the degraded map capability.",
                 "type": "CustomEvent<{ error: unknown }>"
               },
               {
@@ -47331,7 +47331,7 @@
             },
             {
               "name": "label",
-              "description": "Header text used when `label-plural` isn't set, e.g. `\"Sources\"`. Omitting it falls back to\na localized default; an explicit empty string clears it (still overridden by\n`label-plural` when that's set).\n\nType: `string | undefined`"
+              "description": "Header text used when `label-plural` isn't set, e.g. `\"Sources\"`. Omitting it falls back to\na localized default; an explicit empty string uses that localized accessible fallback so the\ndisclosure button always has a name (still overridden by `label-plural` when that's set).\n\nType: `string | undefined`"
             },
             {
               "name": "label-plural",
@@ -47368,7 +47368,7 @@
               },
               {
                 "name": "label",
-                "description": "Header text used when `label-plural` isn't set, e.g. `\"Sources\"`. Omitting it falls back to\na localized default; an explicit empty string clears it (still overridden by\n`label-plural` when that's set).\n\nAttribute: `label`",
+                "description": "Header text used when `label-plural` isn't set, e.g. `\"Sources\"`. Omitting it falls back to\na localized default; an explicit empty string uses that localized accessible fallback so the\ndisclosure button always has a name (still overridden by `label-plural` when that's set).\n\nAttribute: `label`",
                 "type": "string | undefined"
               },
               {