@orangelogic/orange-dam-content-browser-sdk 2.2.8-beta-1 → 2.2.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orangelogic/orange-dam-content-browser-sdk",
-  "version": "2.2.8-beta-1",
+  "version": "2.2.8",
   "description": "OrangeDAM Content Browser SDK source code",
   "main": "build/OrangeDAMContentBrowserSDK.min.js",
   "types": "build/index.d.ts",

package/build/src/utils/focusContainment.cy.d.ts

@@ -1 +0,0 @@
-export {};

package/build/src/utils/focusContainment.d.ts

@@ -1,25 +0,0 @@
-/**
- * Focus-trap-aware popup anchoring (ticket 29KEV1).
- *
- * When the Content Browser SDK opens in popup mode (no `containerId`), its UI is
- * appended to `document.body`, outside any host-page modal. If the host page has
- * an active modal with a focus trap — Drupal's jQuery UI Dialog, Bootstrap,
- * react-focus-lock / focus-trap, a native `<dialog>` opened with `showModal()`,
- * etc. — that trap forces focus back into the modal (or makes the rest of the
- * page `inert`) whenever focus lands on the CBSDK search field, making it
- * impossible to type.
- *
- * Every containment-based focus trap allows focus for elements that are DOM
- * descendants of its container (jQuery UI checks `closest('.ui-dialog')`,
- * focus-trap checks `container.contains(target)`, native modal dialogs don't
- * mark their own subtree `inert`, ...). So the robust, framework-agnostic fix is
- * to mount the CBSDK popup *inside* the active modal container instead of
- * `document.body`.
- */
-/**
- * Finds the active host-page modal that CBSDK should mount inside so its inputs
- * remain focusable. Returns `null` when there is no modal to anchor to (the
- * normal case — CBSDK then mounts to `document.body` as before), or when
- * anchoring would clip CBSDK's fixed overlay.
- */
-export declare function findFocusContainmentHost(doc?: Document): HTMLElement | null;