@wireai/activation 0.3.0 → 0.4.0

package/src/components/loaderChrome.ts

@@ -1,28 +0,0 @@
-/**
- * loaderChrome — the seam that lets a loader center in the FULL flow area instead of
- * the header-offset body it happens to render into.
- *
- * The between-turns loader lives inside the OnboardingScaffold body (so the card↔loader
- * handoff stays one coordinated CardHandoff — see OnboardingFlow). But the body sits
- * BELOW the header (the StepProgress bar), so a loader that only fills the body centers
- * a little low — the "not centralized in the screen" device finding. The scaffold knows
- * its own top chrome, so it publishes a vertical offset here; LoadingBlock reads it and
- * shifts its centered content up by that much, landing it at the true screen center
- * WITHOUT moving the body (the card underneath is untouched, so the handoff never jumps).
- *
- * Default 0: a LoadingBlock rendered OUTSIDE a scaffold (the standalone LoadingScreen used
- * for cold-start / restoring / error) has no header above it, so it already centers in the
- * full area and needs no shift.
- */
-import { createContext, useContext } from "react";
-
-export type LoaderChrome = {
-  /** Vertical shift (px, usually negative = up) that re-centers a loader against the full flow area. */
-  offsetY: number;
-};
-
-const LoaderChromeContext = createContext<LoaderChrome>({ offsetY: 0 });
-
-export const LoaderChromeProvider = LoaderChromeContext.Provider;
-
-export const useLoaderChrome = (): LoaderChrome => useContext(LoaderChromeContext);