import type { CanvasNumericalBrandTheme } from './types';
/**
* Sana Canvas brand tokens for scoped `CanvasProvider` / popup forwarding.
* Values are `var()` references to Sana brand variables — not merged from `defaultCanvasTheme`.
*
* Mirrors only what Sana's stylesheet itself defines: the `neutral` ramp, the `A300` step of
* `primary`/`critical`/`caution`/`positive` (the one step Sana redefines for those families — a
* stronger alpha wash on the matching hue), and the four `system.color.brand.*` tokens Sana
* overrides. Every other key is intentionally omitted — Sana does not define a distinct value
* for it, so writing it here would only reference the very variable being written (a `var()`
* cycle that resolves to invalid, leaking the classic-theme fallback color instead of Sana's).
*
* `action.*` and `selected.*` are deliberately **not** set. Sana's stylesheet does not define
* `--cnvs-brand-action-*` or `--cnvs-sys-color-brand-fg-selected`/`-surface-selected`; those are
* derived downstream from the root theme. Forcing them here would pin values the root is meant
* to own.
*
* Ramp values must reference `base.*` (the underlying palette), never `brand.*` of the same
* name — CanvasProvider writes each entry onto the identically-named `--cnvs-brand-*` CSS
* variable, so referencing `brand.*` here would create that same self-reference cycle. The
* `system.color.brand.*` overrides are the exception: they target *different* CSS variables
* (`--cnvs-sys-color-brand-*`) than the `brand.*` values they reference, so no cycle.
*
* Note this preset only covers brand tokens. The rest of Sana (shape, depth, type, non-brand
* system colors) comes from the stylesheet's `[data-theme="sana-canvas"]` block — pass
* `data-theme` to `CanvasProvider` alongside this preset and it is forwarded to portaled popups
* so the full theme applies there too.
*/
export declare const sanaCanvasNumericalTheme: CanvasNumericalBrandTheme;
/**
* Pass to root `CanvasProvider` to forward Sana brand CSS variables onto popup containers
* (menus, selects, modals, tooltips).
*
* **When to use it**
* - **Required** when you cannot set `data-theme="sana-canvas"` on `` (embedded apps,
* microfrontends, third-party shells). Popups portal to `document.body` and will not inherit
* a nested `data-theme` — this preset copies Sana brand vars onto the popup stack container.
* - Also useful in tests without global Sana CSS, or custom popup hosts outside normal cascade.
*
* **When you can skip it**
* - Prefer setting `data-theme="sana-canvas"` on `` with Sana CSS imported. Popups then
* inherit brand variables from the document and no `theme` prop is needed.
*
* Pass `data-theme="sana-canvas"` alongside it. That attribute is forwarded to popup stack
* containers, so the rest of Sana (shape, depth, type, non-brand system colors) applies to
* portaled content through the stylesheet's own `[data-theme="sana-canvas"]` block — this preset
* covers brand tokens, the attribute covers everything else.
*
* `action.*` and selected-state tokens are not set by this preset — Sana does not define them,
* and they resolve from the root theme.
*
* @example
* ```tsx
* // Preferred — control
* import '@workday/canvas-tokens-web/css/sana/_variables.css';
* //
*
*
* // No access to — pass both for full parity, including portaled popups
*
*
*
* ```
*/
export declare const sanaCanvasProviderTheme: CanvasNumericalBrandTheme;
//# sourceMappingURL=sanaTheme.d.ts.map