@aurodesignsystem-dev/auro-formkit 0.0.0-pr1524.0 → 0.0.0-pr1530.0

package/custom-elements.json

@@ -1306,20 +1306,6 @@
             {
               "kind": "method",
               "name": "handleMenuOptions",
-              "parameters": [
-                {
-                  "name": "{ preferComboboxValue = false }",
-                  "default": "{}"
-                },
-                {
-                  "description": "Optional flag bag.",
-                  "name": "root0",
-                  "optional": true,
-                  "type": {
-                    "text": "@param {boolean} [root0.preferComboboxValue=false] - When true, a match on `this.value` wins the tie-break over `this.input.value` (used by handleSlotChange on mount / re-mount).\n   * "
-                  }
-                }
-              ],
               "description": "Processes hidden state of all menu options and determines if there are any available options not hidden.",
               "privacy": "private",
               "return": {
@@ -5570,7 +5556,7 @@
             {
               "kind": "method",
               "name": "_getBlackoutSet",
-              "description": "Returns a memoized Set of blackout timestamps (seconds) drawn from both\nthe legacy `disabledDays` array and the datepicker's ISO `blackoutDates`.\nThe cache invalidates when either source array's reference changes, which\nmatches Lit's own reactive identity semantics for array properties.",
+              "description": "Returns a memoized Set of blackout timestamps (seconds) drawn from both\nthe legacy `disabledDays` array and the datepicker's ISO `blackoutDates`.\n\nThe cache invalidates on **reference identity** — only when the\nconsumer reassigns the array (`el.blackoutDates = [...]`), matching\nLit's own reactivity semantics for array properties. In-place mutations\non the existing array (`push`, `splice`, index assignment) will NOT\ninvalidate the cache and the new entries will be silently ignored.\nConsumers must reassign to update — see the JSDoc on\n`auro-datepicker.blackoutDates` for the recommended pattern.\n\nA shallow-equality tier was considered but rejected: it would run\nO(N) work on every cell render (this method is called per-cell via\n`isBlackout()`) and still wouldn't catch same-length value swaps,\noffering a false sense of safety.",
               "privacy": "private",
               "return": {
                 "type": {
@@ -5946,7 +5932,7 @@
                   }
                 }
               ],
-              "description": "Debounced version of announceSelection for focus navigation.\nUses the assertive live region with a 150ms debounce so only the\nfinal cell after rapid arrow-key traversal is announced. We\noriginally tried aria-live=\"polite\" here, but VoiceOver treats\npolite as \"wait until idle\" — which never happens during active\nkeyboard navigation — so the announcements were silently dropped.",
+              "description": "Debounced version of announceSelection for focus navigation.\nUses the assertive live region with a 150ms debounce so only the\nfinal cell after rapid arrow-key traversal is announced. We\noriginally tried aria-live=\"polite\" here, but VoiceOver treats\npolite as \"wait until idle\" — which never happens during active\nkeyboard navigation — so the announcements were silently dropped.\n\nThis is a documented deviation from WCAG 2.1 SC 4.1.3, which\nprefers `polite` for status messages. See the \"Documented\nDeviation\" section in components/datepicker/docs/pages/accessibility.md.",
               "privacy": "private",
               "return": {
                 "type": {
@@ -7528,7 +7514,7 @@
               "type": {
                 "text": "array"
               },
-              "description": "Array of dates that cannot be selected. Dates should be in ISO format (YYYY-MM-DD).",
+              "description": "Array of dates that cannot be selected. Dates should be in ISO format (YYYY-MM-DD).\n\n**Immutable update required.** The datepicker treats this array as\nimmutable and memoizes a lookup Set keyed on the array's reference\nidentity — matching Lit's own reactivity semantics for array\nproperties. In-place mutations (`blackoutDates.push(...)`,\n`blackoutDates[i] = ...`, `blackoutDates.splice(...)`) will not\ninvalidate the cache and the new entries will be silently ignored.\nTo update, reassign the property: `el.blackoutDates = [...el.blackoutDates, '2024-12-25']`.",
               "default": "[]",
               "attribute": "blackoutDates",
               "reflects": true
@@ -8192,7 +8178,7 @@
               "type": {
                 "text": "array"
               },
-              "description": "Array of dates that cannot be selected. Dates should be in ISO format (YYYY-MM-DD).",
+              "description": "Array of dates that cannot be selected. Dates should be in ISO format (YYYY-MM-DD).\n\n**Immutable update required.** The datepicker treats this array as\nimmutable and memoizes a lookup Set keyed on the array's reference\nidentity — matching Lit's own reactivity semantics for array\nproperties. In-place mutations (`blackoutDates.push(...)`,\n`blackoutDates[i] = ...`, `blackoutDates.splice(...)`) will not\ninvalidate the cache and the new entries will be silently ignored.\nTo update, reassign the property: `el.blackoutDates = [...el.blackoutDates, '2024-12-25']`.",
               "default": "[]",
               "fieldName": "blackoutDates"
             },
@@ -8816,7 +8802,7 @@
           "type": {
             "text": "object"
           },
-          "default": "{ Escape(component, evt, ctx) { if (!ctx.isExpanded) { return; } // Stop propagation so parent containers (auro-dialog, auro-drawer) // don't also react to Escape. evt.stopPropagation(); evt.preventDefault(); component.hideBib(); }, Enter(component, evt, ctx) { if (ctx.isExpanded) { return; } // Only open from the trigger input, not the clear button or other internal elements. // evt.target is retargeted to the host in shadow DOM, so use composedPath() // to find the real origin. The clear button is rendered with class \"clearBtn\". const path = evt.composedPath(); if (path.some(el => el.classList?.contains('clearBtn'))) { return; } evt.preventDefault(); component.dropdown.show(); }, ' '(component, evt, ctx) { if (ctx.isExpanded) { return; } // Only open from the trigger input, not the clear button or other internal elements. // evt.target is retargeted to the host in shadow DOM, so use composedPath() // to find the real origin. The clear button is rendered with class \"clearBtn\". const path = evt.composedPath(); if (path.some(el => el.classList?.contains('clearBtn'))) { return; } evt.preventDefault(); component.dropdown.show(); }, }"
+          "default": "{ Escape(component, evt, ctx) { if (!ctx.isExpanded) { return; } // Stop propagation so parent containers (auro-dialog, auro-drawer) // don't also react to Escape. evt.stopPropagation(); evt.preventDefault(); // Signal to the visibility-change handler in auro-datepicker.js that // focus should be restored to the trigger regardless of hasFocus. // hidePopover() (desktop non-modal path) does not auto-restore focus, // and hiding the grid's popover ancestor drops focus to <body>. That // synchronously fires focusout on the datepicker host — clearing // hasFocus — before updated() runs, which would otherwise skip the // input refocus. Native <dialog>.close() (modal path) restores focus // itself, but the flag is harmless there. component._restoreFocusOnClose = true; component.hideBib(); }, Enter(component, evt, ctx) { if (ctx.isExpanded) { return; } // Only open from the trigger input, not the clear button or other internal elements. // evt.target is retargeted to the host in shadow DOM, so use composedPath() // to find the real origin. The clear button is rendered with class \"clearBtn\". const path = evt.composedPath(); if (path.some(el => el.classList?.contains('clearBtn'))) { return; } evt.preventDefault(); component.dropdown.show(); }, ' '(component, evt, ctx) { if (ctx.isExpanded) { return; } // Only open from the trigger input, not the clear button or other internal elements. // evt.target is retargeted to the host in shadow DOM, so use composedPath() // to find the real origin. The clear button is rendered with class \"clearBtn\". const path = evt.composedPath(); if (path.some(el => el.classList?.contains('clearBtn'))) { return; } evt.preventDefault(); component.dropdown.show(); }, }"
         }
       ],
       "exports": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aurodesignsystem-dev/auro-formkit",
-  "version": "0.0.0-pr1524.0",
+  "version": "0.0.0-pr1530.0",
   "description": "A collection of web components used to build forms.",
   "homepage": "https://github.com/AlaskaAirlines/auro-formkit#readme",
   "bugs": {