@haiilo/catalyst 10.31.0 → 10.31.1

package/dist/types/components/cat-dropdown/cat-dropdown.d.ts

@@ -14,6 +14,12 @@ export declare class CatDropdown {
     private content;
     private trap?;
     private isOpen;
+    /**
+     * Tracking the origin of opening the dropdown and specify if initial focus should be set.
+     * Currently we set it only when the origin is keyboard.
+     * We might not need to track this in future when focus-visible support is improved across browsers
+     */
+    private hasInitialFocus;
     /**
      * The placement of the dropdown.
      */
@@ -38,6 +44,10 @@ export declare class CatDropdown {
     /**
      * No element in dropdown will receive focus when dropdown is open.
      * By default, the first element in tab order will receive a focus.
+     * @deprecated
+     * Using noInitialFocus property would be a bad practice from a11y perspective.
+     * We always want visible focus to jump inside the dropdown when user uses keyboard and noInitialFocus allows to turn it off which might introduce a bug.
+     * hasInitialFocus should resolve the cause of the original problem instead.
      */
     noInitialFocus: boolean;
     /**
@@ -59,8 +69,9 @@ export declare class CatDropdown {
     toggle(): Promise<void>;
     /**
      * Opens the dropdown.
+     * @param isFocusVisible is dropdown should receive visible focus when it's opened.
      */
-    open(): Promise<void>;
+    open(isFocusVisible?: boolean): Promise<void>;
     /**
      * Closes the dropdown.
      */
@@ -69,6 +80,7 @@ export declare class CatDropdown {
     componentDidLoad(): void;
     private get contentId();
     private initTrigger;
+    private isEventOriginFromKeyboard;
     private initAnchor;
     private findTrigger;
     private update;

package/dist/types/components.d.ts

@@ -699,6 +699,7 @@ export namespace Components {
         "noAutoClose": boolean;
         /**
           * No element in dropdown will receive focus when dropdown is open. By default, the first element in tab order will receive a focus.
+          * @deprecated Using noInitialFocus property would be a bad practice from a11y perspective. We always want visible focus to jump inside the dropdown when user uses keyboard and noInitialFocus allows to turn it off which might introduce a bug. hasInitialFocus should resolve the cause of the original problem instead.
          */
         "noInitialFocus": boolean;
         /**
@@ -711,8 +712,9 @@ export namespace Components {
         "noReturnFocus": boolean;
         /**
           * Opens the dropdown.
+          * @param isFocusVisible is dropdown should receive visible focus when it's opened.
          */
-        "open": () => Promise<void>;
+        "open": (isFocusVisible?: boolean) => Promise<void>;
         /**
           * Allow overflow when dropdown is open.
          */
@@ -3032,6 +3034,7 @@ declare namespace LocalJSX {
         "noAutoClose"?: boolean;
         /**
           * No element in dropdown will receive focus when dropdown is open. By default, the first element in tab order will receive a focus.
+          * @deprecated Using noInitialFocus property would be a bad practice from a11y perspective. We always want visible focus to jump inside the dropdown when user uses keyboard and noInitialFocus allows to turn it off which might introduce a bug. hasInitialFocus should resolve the cause of the original problem instead.
          */
         "noInitialFocus"?: boolean;
         /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haiilo/catalyst",
-  "version": "10.31.0",
+  "version": "10.31.1",
   "description": "Catalyst Design System",
   "license": "MIT",
   "repository": {
@@ -39,7 +39,7 @@
     "sanitize.css": "13.0.0",
     "tabbable": "6.2.0",
     "toastify-js": "1.12.0",
-    "@haiilo/catalyst-tokens": "10.31.0"
+    "@haiilo/catalyst-tokens": "10.31.1"
   },
   "devDependencies": {
     "@babel/core": "^7.24.7",