@aurodesignsystem-dev/auro-formkit 0.0.0-pr1346.13 → 0.0.0-pr1346.14

package/components/dropdown/demo/index.min.js

@@ -3156,45 +3156,70 @@ class AuroDropdownBib extends i {
   firstUpdated(changedProperties) {
     super.firstUpdated(changedProperties);
 
-    // Handle ESC key via dialog's cancel event
     const dialog = this.shadowRoot.querySelector('dialog');
+    this._setupCancelHandler(dialog);
+    this._setupKeyboardBridge(dialog);
+
+    this.dispatchEvent(new CustomEvent('auro-dropdownbib-connected', {
+      bubbles: true,
+      composed: true,
+      detail: {
+        element: this
+      }
+    }));
+  }
+
+  /**
+   * Forwards the dialog's native `cancel` event (fired on ESC) as
+   * an `auro-bib-cancel` custom event so parent components can close.
+   * @param {HTMLDialogElement} dialog
+   * @private
+   */
+  _setupCancelHandler(dialog) {
     dialog.addEventListener('cancel', (event) => {
-      // Let parent handle closing
       event.preventDefault();
       this.dispatchEvent(new CustomEvent('auro-bib-cancel', {
         bubbles: true,
         composed: true
       }));
     });
+  }
 
-    // showModal() creates a closed focus scope — keyboard events inside
-    // the dialog's shadow DOM do NOT bubble out to the combobox/select
-    // keydown handlers in the parent shadow DOM. This handler bridges
-    // that gap by re-dispatching navigation keys so they cross the
-    // shadow boundary and reach the menu navigation logic in the parent
-    // component.
-    //
-    // The trade-off: intercepting these keys means native keyboard
-    // behaviors that would normally "just work" must be manually
-    // re-implemented here:
-    //
-    // - Enter on buttons: Custom elements (auro-button) don't get the
-    //   native Enter→click that <button> provides, so we call .click()
-    //   directly when Enter is pressed on a button-like element.
-    //
-    // - Tab: Intercepted and re-dispatched so parent components
-    //   (select/combobox) can select the active option and close the
-    //   dialog. The <dialog> provides containment and isolation
-    //   (inert background, VoiceOver focus trapping, top layer), while
-    //   the content inside is a role="listbox" navigated via
-    //   aria-activedescendant (options are not focusable). Tab keyboard
-    //   behavior follows listbox conventions (select + close) because
-    //   the dialog's native Tab trap only cycles between the close
-    //   button and browser chrome.
-    //
-    // - Escape: The native <dialog> fires a `cancel` event on ESC
-    //   (handled above), so the re-dispatched Escape is a secondary
-    //   path for parent components that also listen for Escape keydown.
+  /**
+   * showModal() creates a closed focus scope — keyboard events inside
+   * the dialog's shadow DOM do NOT bubble out to the combobox/select
+   * keydown handlers in the parent shadow DOM. This handler bridges
+   * that gap by re-dispatching navigation keys so they cross the
+   * shadow boundary and reach the menu navigation logic in the parent
+   * component.
+   *
+   * The trade-off: intercepting these keys means native keyboard
+   * behaviors that would normally "just work" must be manually
+   * re-implemented here:
+   *
+   * - Enter on buttons: Custom elements (auro-button) don't get the
+   *   native Enter→click that <button> provides, so we call .click()
+   *   directly when Enter is pressed on a button-like element.
+   *
+   * - Tab: Intercepted and re-dispatched so parent components
+   *   (select/combobox) can select the active option and close the
+   *   dialog. The <dialog> provides containment and isolation
+   *   (inert background, VoiceOver focus trapping, top layer), while
+   *   the content inside is a role="listbox" navigated via
+   *   aria-activedescendant (options are not focusable). Tab keyboard
+   *   behavior follows listbox conventions (select + close) because
+   *   the dialog's native Tab trap only cycles between the close
+   *   button and browser chrome.
+   *
+   * - Escape: The native <dialog> fires a `cancel` event on ESC
+   *   (handled by _setupCancelHandler), so the re-dispatched Escape
+   *   is a secondary path for parent components that also listen for
+   *   Escape keydown.
+   *
+   * @param {HTMLDialogElement} dialog
+   * @private
+   */
+  _setupKeyboardBridge(dialog) {
     const navKeys = new Set([
       'ArrowUp',
       'ArrowDown',
@@ -3202,6 +3227,7 @@ class AuroDropdownBib extends i {
       'Escape',
       'Tab'
     ]);
+
     dialog.addEventListener('keydown', (event) => {
       if (!navKeys.has(event.key)) {
         return;
@@ -3236,15 +3262,6 @@ class AuroDropdownBib extends i {
       });
       this.dispatchEvent(newEvent);
     });
-
-    // Dispatch a custom event when the component is connected
-    this.dispatchEvent(new CustomEvent('auro-dropdownbib-connected', {
-      bubbles: true,
-      composed: true,
-      detail: {
-        element: this
-      }
-    }));
   }
 
   /**
@@ -3596,7 +3613,7 @@ class AuroHelpText extends i {
   }
 }
 
-var formkitVersion = '202603091734';
+var formkitVersion = '202603091748';
 
 class AuroElement extends i {
   static get properties() {

package/components/dropdown/dist/auro-dropdownBib.d.ts

@@ -73,6 +73,48 @@ export class AuroDropdownBib extends LitElement {
     updated(changedProperties: any): void;
     bibTemplate: any;
     firstUpdated(changedProperties: any): void;
+    /**
+     * Forwards the dialog's native `cancel` event (fired on ESC) as
+     * an `auro-bib-cancel` custom event so parent components can close.
+     * @param {HTMLDialogElement} dialog
+     * @private
+     */
+    private _setupCancelHandler;
+    /**
+     * showModal() creates a closed focus scope — keyboard events inside
+     * the dialog's shadow DOM do NOT bubble out to the combobox/select
+     * keydown handlers in the parent shadow DOM. This handler bridges
+     * that gap by re-dispatching navigation keys so they cross the
+     * shadow boundary and reach the menu navigation logic in the parent
+     * component.
+     *
+     * The trade-off: intercepting these keys means native keyboard
+     * behaviors that would normally "just work" must be manually
+     * re-implemented here:
+     *
+     * - Enter on buttons: Custom elements (auro-button) don't get the
+     *   native Enter→click that <button> provides, so we call .click()
+     *   directly when Enter is pressed on a button-like element.
+     *
+     * - Tab: Intercepted and re-dispatched so parent components
+     *   (select/combobox) can select the active option and close the
+     *   dialog. The <dialog> provides containment and isolation
+     *   (inert background, VoiceOver focus trapping, top layer), while
+     *   the content inside is a role="listbox" navigated via
+     *   aria-activedescendant (options are not focusable). Tab keyboard
+     *   behavior follows listbox conventions (select + close) because
+     *   the dialog's native Tab trap only cycles between the close
+     *   button and browser chrome.
+     *
+     * - Escape: The native <dialog> fires a `cancel` event on ESC
+     *   (handled by _setupCancelHandler), so the re-dispatched Escape
+     *   is a secondary path for parent components that also listen for
+     *   Escape keydown.
+     *
+     * @param {HTMLDialogElement} dialog
+     * @private
+     */
+    private _setupKeyboardBridge;
     /**
      * Blocks touch-driven page scroll while a fullscreen modal dialog is open.
      *

package/components/dropdown/dist/index.js

@@ -3065,45 +3065,70 @@ class AuroDropdownBib extends LitElement {
   firstUpdated(changedProperties) {
     super.firstUpdated(changedProperties);
 
-    // Handle ESC key via dialog's cancel event
     const dialog = this.shadowRoot.querySelector('dialog');
+    this._setupCancelHandler(dialog);
+    this._setupKeyboardBridge(dialog);
+
+    this.dispatchEvent(new CustomEvent('auro-dropdownbib-connected', {
+      bubbles: true,
+      composed: true,
+      detail: {
+        element: this
+      }
+    }));
+  }
+
+  /**
+   * Forwards the dialog's native `cancel` event (fired on ESC) as
+   * an `auro-bib-cancel` custom event so parent components can close.
+   * @param {HTMLDialogElement} dialog
+   * @private
+   */
+  _setupCancelHandler(dialog) {
     dialog.addEventListener('cancel', (event) => {
-      // Let parent handle closing
       event.preventDefault();
       this.dispatchEvent(new CustomEvent('auro-bib-cancel', {
         bubbles: true,
         composed: true
       }));
     });
+  }
 
-    // showModal() creates a closed focus scope — keyboard events inside
-    // the dialog's shadow DOM do NOT bubble out to the combobox/select
-    // keydown handlers in the parent shadow DOM. This handler bridges
-    // that gap by re-dispatching navigation keys so they cross the
-    // shadow boundary and reach the menu navigation logic in the parent
-    // component.
-    //
-    // The trade-off: intercepting these keys means native keyboard
-    // behaviors that would normally "just work" must be manually
-    // re-implemented here:
-    //
-    // - Enter on buttons: Custom elements (auro-button) don't get the
-    //   native Enter→click that <button> provides, so we call .click()
-    //   directly when Enter is pressed on a button-like element.
-    //
-    // - Tab: Intercepted and re-dispatched so parent components
-    //   (select/combobox) can select the active option and close the
-    //   dialog. The <dialog> provides containment and isolation
-    //   (inert background, VoiceOver focus trapping, top layer), while
-    //   the content inside is a role="listbox" navigated via
-    //   aria-activedescendant (options are not focusable). Tab keyboard
-    //   behavior follows listbox conventions (select + close) because
-    //   the dialog's native Tab trap only cycles between the close
-    //   button and browser chrome.
-    //
-    // - Escape: The native <dialog> fires a `cancel` event on ESC
-    //   (handled above), so the re-dispatched Escape is a secondary
-    //   path for parent components that also listen for Escape keydown.
+  /**
+   * showModal() creates a closed focus scope — keyboard events inside
+   * the dialog's shadow DOM do NOT bubble out to the combobox/select
+   * keydown handlers in the parent shadow DOM. This handler bridges
+   * that gap by re-dispatching navigation keys so they cross the
+   * shadow boundary and reach the menu navigation logic in the parent
+   * component.
+   *
+   * The trade-off: intercepting these keys means native keyboard
+   * behaviors that would normally "just work" must be manually
+   * re-implemented here:
+   *
+   * - Enter on buttons: Custom elements (auro-button) don't get the
+   *   native Enter→click that <button> provides, so we call .click()
+   *   directly when Enter is pressed on a button-like element.
+   *
+   * - Tab: Intercepted and re-dispatched so parent components
+   *   (select/combobox) can select the active option and close the
+   *   dialog. The <dialog> provides containment and isolation
+   *   (inert background, VoiceOver focus trapping, top layer), while
+   *   the content inside is a role="listbox" navigated via
+   *   aria-activedescendant (options are not focusable). Tab keyboard
+   *   behavior follows listbox conventions (select + close) because
+   *   the dialog's native Tab trap only cycles between the close
+   *   button and browser chrome.
+   *
+   * - Escape: The native <dialog> fires a `cancel` event on ESC
+   *   (handled by _setupCancelHandler), so the re-dispatched Escape
+   *   is a secondary path for parent components that also listen for
+   *   Escape keydown.
+   *
+   * @param {HTMLDialogElement} dialog
+   * @private
+   */
+  _setupKeyboardBridge(dialog) {
     const navKeys = new Set([
       'ArrowUp',
       'ArrowDown',
@@ -3111,6 +3136,7 @@ class AuroDropdownBib extends LitElement {
       'Escape',
       'Tab'
     ]);
+
     dialog.addEventListener('keydown', (event) => {
       if (!navKeys.has(event.key)) {
         return;
@@ -3145,15 +3171,6 @@ class AuroDropdownBib extends LitElement {
       });
       this.dispatchEvent(newEvent);
     });
-
-    // Dispatch a custom event when the component is connected
-    this.dispatchEvent(new CustomEvent('auro-dropdownbib-connected', {
-      bubbles: true,
-      composed: true,
-      detail: {
-        element: this
-      }
-    }));
   }
 
   /**
@@ -3505,7 +3522,7 @@ class AuroHelpText extends LitElement {
   }
 }
 
-var formkitVersion = '202603091734';
+var formkitVersion = '202603091748';
 
 class AuroElement extends LitElement {
   static get properties() {

package/components/dropdown/dist/registered.js

@@ -3065,45 +3065,70 @@ class AuroDropdownBib extends LitElement {
   firstUpdated(changedProperties) {
     super.firstUpdated(changedProperties);
 
-    // Handle ESC key via dialog's cancel event
     const dialog = this.shadowRoot.querySelector('dialog');
+    this._setupCancelHandler(dialog);
+    this._setupKeyboardBridge(dialog);
+
+    this.dispatchEvent(new CustomEvent('auro-dropdownbib-connected', {
+      bubbles: true,
+      composed: true,
+      detail: {
+        element: this
+      }
+    }));
+  }
+
+  /**
+   * Forwards the dialog's native `cancel` event (fired on ESC) as
+   * an `auro-bib-cancel` custom event so parent components can close.
+   * @param {HTMLDialogElement} dialog
+   * @private
+   */
+  _setupCancelHandler(dialog) {
     dialog.addEventListener('cancel', (event) => {
-      // Let parent handle closing
       event.preventDefault();
       this.dispatchEvent(new CustomEvent('auro-bib-cancel', {
         bubbles: true,
         composed: true
       }));
     });
+  }
 
-    // showModal() creates a closed focus scope — keyboard events inside
-    // the dialog's shadow DOM do NOT bubble out to the combobox/select
-    // keydown handlers in the parent shadow DOM. This handler bridges
-    // that gap by re-dispatching navigation keys so they cross the
-    // shadow boundary and reach the menu navigation logic in the parent
-    // component.
-    //
-    // The trade-off: intercepting these keys means native keyboard
-    // behaviors that would normally "just work" must be manually
-    // re-implemented here:
-    //
-    // - Enter on buttons: Custom elements (auro-button) don't get the
-    //   native Enter→click that <button> provides, so we call .click()
-    //   directly when Enter is pressed on a button-like element.
-    //
-    // - Tab: Intercepted and re-dispatched so parent components
-    //   (select/combobox) can select the active option and close the
-    //   dialog. The <dialog> provides containment and isolation
-    //   (inert background, VoiceOver focus trapping, top layer), while
-    //   the content inside is a role="listbox" navigated via
-    //   aria-activedescendant (options are not focusable). Tab keyboard
-    //   behavior follows listbox conventions (select + close) because
-    //   the dialog's native Tab trap only cycles between the close
-    //   button and browser chrome.
-    //
-    // - Escape: The native <dialog> fires a `cancel` event on ESC
-    //   (handled above), so the re-dispatched Escape is a secondary
-    //   path for parent components that also listen for Escape keydown.
+  /**
+   * showModal() creates a closed focus scope — keyboard events inside
+   * the dialog's shadow DOM do NOT bubble out to the combobox/select
+   * keydown handlers in the parent shadow DOM. This handler bridges
+   * that gap by re-dispatching navigation keys so they cross the
+   * shadow boundary and reach the menu navigation logic in the parent
+   * component.
+   *
+   * The trade-off: intercepting these keys means native keyboard
+   * behaviors that would normally "just work" must be manually
+   * re-implemented here:
+   *
+   * - Enter on buttons: Custom elements (auro-button) don't get the
+   *   native Enter→click that <button> provides, so we call .click()
+   *   directly when Enter is pressed on a button-like element.
+   *
+   * - Tab: Intercepted and re-dispatched so parent components
+   *   (select/combobox) can select the active option and close the
+   *   dialog. The <dialog> provides containment and isolation
+   *   (inert background, VoiceOver focus trapping, top layer), while
+   *   the content inside is a role="listbox" navigated via
+   *   aria-activedescendant (options are not focusable). Tab keyboard
+   *   behavior follows listbox conventions (select + close) because
+   *   the dialog's native Tab trap only cycles between the close
+   *   button and browser chrome.
+   *
+   * - Escape: The native <dialog> fires a `cancel` event on ESC
+   *   (handled by _setupCancelHandler), so the re-dispatched Escape
+   *   is a secondary path for parent components that also listen for
+   *   Escape keydown.
+   *
+   * @param {HTMLDialogElement} dialog
+   * @private
+   */
+  _setupKeyboardBridge(dialog) {
     const navKeys = new Set([
       'ArrowUp',
       'ArrowDown',
@@ -3111,6 +3136,7 @@ class AuroDropdownBib extends LitElement {
       'Escape',
       'Tab'
     ]);
+
     dialog.addEventListener('keydown', (event) => {
       if (!navKeys.has(event.key)) {
         return;
@@ -3145,15 +3171,6 @@ class AuroDropdownBib extends LitElement {
       });
       this.dispatchEvent(newEvent);
     });
-
-    // Dispatch a custom event when the component is connected
-    this.dispatchEvent(new CustomEvent('auro-dropdownbib-connected', {
-      bubbles: true,
-      composed: true,
-      detail: {
-        element: this
-      }
-    }));
   }
 
   /**
@@ -3505,7 +3522,7 @@ class AuroHelpText extends LitElement {
   }
 }
 
-var formkitVersion = '202603091734';
+var formkitVersion = '202603091748';
 
 class AuroElement extends LitElement {
   static get properties() {