@pantheon-systems/pds-toolkit-react 2.0.0-alpha.79 → 2.0.0-alpha.80

package/dist/libs/components/NestedOverlayContext.d.ts

@@ -0,0 +1,14 @@
+/**
+ * True when rendered as a descendant of a Modal/Drawer/BottomSheet/
+ * FullScreenOverlay's own content — i.e. genuinely nested inside another
+ * overlay, not just present somewhere on the page while one happens to be
+ * open elsewhere. Those four overlays wrap their content in
+ * `NestedOverlayContext.Provider value={true}`; nothing else needs to
+ * provide it.
+ *
+ * Consumed via `useOverlayZIndex`, not directly — see that hook for why this
+ * exists (floating panels portaled out of these overlays' own z-indexed box
+ * need to know when to elevate above it).
+ */
+export declare const NestedOverlayContext: import("react").Context<boolean>;
+export declare const useIsNestedInOverlay: () => boolean;

package/dist/libs/components/useOverlayZIndex.d.ts

@@ -0,0 +1,16 @@
+/**
+ * z-index for a floating panel (dropdown, combobox, menu, popover, calendar):
+ * `defaultZIndex` normally, or `--pds-z-index-active-panel` when
+ * `useIsNestedInOverlay()` confirms this panel is genuinely nested inside
+ * another overlay's own content (Modal, Drawer, BottomSheet,
+ * FullScreenOverlay) — otherwise it would lose the z-index comparison to
+ * that overlay and render behind it (those overlays portal a panel opened
+ * from inside them as a SIBLING of their own z-indexed box, not a
+ * descendant of it, so simple DOM nesting doesn't resolve the stacking on
+ * its own).
+ *
+ * A standalone, page-level panel keeps `defaultZIndex`, so it can't outrank
+ * a Modal that opens afterward elsewhere on the page — only a panel that's
+ * actually part of an overlay's own content gets elevated.
+ */
+export declare const useOverlayZIndex: (defaultZIndex: string) => string;

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@pantheon-systems/pds-toolkit-react",
 	"technology": "React",
-	"version": "2.0.0-alpha.79",
+	"version": "2.0.0-alpha.80",
 	"description": "PDS toolkit built using the React framework",
 	"publishConfig": {
 		"access": "public",