@aceshooting/lyra-ui 9.1.0 → 9.1.1

package/web-types.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/web-types",
   "name": "@aceshooting/lyra-ui",
-  "version": "9.1.0",
+  "version": "9.1.1",
   "description-markup": "markdown",
   "contributions": {
     "html": {
@@ -1289,7 +1289,7 @@
         },
         {
           "name": "lr-attachment-trigger",
-          "description": "`<lr-attachment-trigger>` — a compact attach affordance designed for a\nchat composer's leading slot (see `<lr-chat-composer>`'s own `leading`\nslot, which this drops straight into, though this component has no code\ndependency on it). Its shape adapts to how many attachment `capabilities`\nare configured:\n - Exactly one capability: a single plain icon button ([part='trigger']).\n   Activating it performs that capability's action directly.\n - More than one: a small anchored menu ([part='menu'], composed from\n   `<lr-dropdown>`/`<lr-menu>`/`<lr-menu-item>`) listing each capability as a row.\n\nTwo of the four capabilities (`files`, `image`) are file-picker-backed:\nactivating them opens a hidden native `<input type=\"file\">` via a\nsynthetic `.click()`, and the resulting selection is re-emitted as\n`lr-files`. `accept` is shared across both — `image` defaults it to\n`'image/*'` unless the `accept` prop overrides it, `files` always uses\n`accept` as-is (empty means \"any file type\", matching a bare native\n`<input type=\"file\">` with no `accept` attribute).\n\n**`camera`/`audio` are scope-limited by design.** This component does not\nimplement any camera or microphone capture UI itself — no `getUserMedia`,\nno `<input capture>` — because that's entirely a host/browser concern with\nno single right answer (a desktop web app, a mobile PWA, and a native\nwrapper all want different things here). Activating `camera` fires\n`lr-camera-request`; activating `audio` fires `lr-audio-request`. The\nhost owns everything from that point on — typically opening\n`<lr-push-to-talk>` in a `<lr-overlay>`/popover for `audio`, then\nhanding the resulting blob to something like `<lr-attachment-chip>`.\n\n---\n\n**Component metadata**\n\n- Status: `stable`\n- Since: `4.0.0`\n- Rationale: This exact lr-* tag appears in a published Lyra release manifest and remains a supported public contract under semver.\n- Graduation: Already stable; it retains that status while its documented behavior, accessibility, compatibility, and cross-browser support remain part of the public contract.\n\n---\n\n**CSS Shadow Parts**\n\n| Name | Description |\n| --- | --- |\n| `expand-icon` | The disclosure chevron inside the multi-capability trigger button. Only rendered when `capabilities.length > 1`. |\n| `hidden-input` | The internal native `<input type=\"file\">` that actually opens the OS file picker. Hidden (`display: none`) by default; exposed as a part only so a consumer can override that with `::part(hidden-input)` in the unlikely case their integration needs to. `accessibleLabel` supplies an accessible-name override for either trigger shape. A host `aria-label`, including an explicit empty value, wins over it. |\n| `menu` | The `<lr-dropdown>` shell. Only rendered when `capabilities.length > 1`. |\n| `menu-trigger` | The multi-capability button slotted into `<lr-dropdown>`'s `trigger` slot. Only rendered when `capabilities.length > 1`. |\n| `trigger` | The single-capability icon button. Only rendered when `capabilities.length === 1`. |",
+          "description": "`<lr-attachment-trigger>` — a compact attach affordance designed for a\nchat composer's start slot (see `<lr-chat-composer>`'s own `start`\nslot, which this drops straight into, though this component has no code\ndependency on it). Its shape adapts to how many attachment `capabilities`\nare configured:\n - Exactly one capability: a single plain icon button ([part='trigger']).\n   Activating it performs that capability's action directly.\n - More than one: a small anchored menu ([part='menu'], composed from\n   `<lr-dropdown>`/`<lr-menu>`/`<lr-menu-item>`) listing each capability as a row.\n\nTwo of the four capabilities (`files`, `image`) are file-picker-backed:\nactivating them opens a hidden native `<input type=\"file\">` via a\nsynthetic `.click()`, and the resulting selection is re-emitted as\n`lr-files`. `accept` is shared across both — `image` defaults it to\n`'image/*'` unless the `accept` prop overrides it, `files` always uses\n`accept` as-is (empty means \"any file type\", matching a bare native\n`<input type=\"file\">` with no `accept` attribute).\n\n**`camera`/`audio` are scope-limited by design.** This component does not\nimplement any camera or microphone capture UI itself — no `getUserMedia`,\nno `<input capture>` — because that's entirely a host/browser concern with\nno single right answer (a desktop web app, a mobile PWA, and a native\nwrapper all want different things here). Activating `camera` fires\n`lr-camera-request`; activating `audio` fires `lr-audio-request`. The\nhost owns everything from that point on — typically opening\n`<lr-push-to-talk>` in a `<lr-overlay>`/popover for `audio`, then\nhanding the resulting blob to something like `<lr-attachment-chip>`.\n\n---\n\n**Component metadata**\n\n- Status: `stable`\n- Since: `4.0.0`\n- Rationale: This exact lr-* tag appears in a published Lyra release manifest and remains a supported public contract under semver.\n- Graduation: Already stable; it retains that status while its documented behavior, accessibility, compatibility, and cross-browser support remain part of the public contract.\n\n---\n\n**CSS Shadow Parts**\n\n| Name | Description |\n| --- | --- |\n| `expand-icon` | The disclosure chevron inside the multi-capability trigger button. Only rendered when `capabilities.length > 1`. |\n| `hidden-input` | The internal native `<input type=\"file\">` that actually opens the OS file picker. Hidden (`display: none`) by default; exposed as a part only so a consumer can override that with `::part(hidden-input)` in the unlikely case their integration needs to. `accessibleLabel` supplies an accessible-name override for either trigger shape. A host `aria-label`, including an explicit empty value, wins over it. |\n| `menu` | The `<lr-dropdown>` shell. Only rendered when `capabilities.length > 1`. |\n| `menu-trigger` | The multi-capability button slotted into `<lr-dropdown>`'s `trigger` slot. Only rendered when `capabilities.length > 1`. |\n| `trigger` | The single-capability icon button. Only rendered when `capabilities.length === 1`. |",
           "attributes": [
             {
               "name": "accept",