import { type GlassSurfaceProps } from "./glass-surface.shared.js";
export type { GlassLayer, GlassSurfaceProps } from "./glass-surface-props.js";
/**
 * The host every kit glass surface renders through (a Card, a Dialog, a Popover's card, the
 * Navbar, an option list and the rest), painting its layer's material behind its children.
 *
 * On the web the material is Dark Factory's plain frost (a 24 px backdrop blur with no
 * saturation shift, the layer's tint painted over it, so the blur samples the page and never
 * the surface's own fill, and a 1 px inset hairline). On iOS 26 and later it is
 * Apple's Liquid Glass through expo-glass-effect for the functional, control and dense
 * layers, and expo-blur's frost with a specular rim for content and static surfaces and
 * before iOS 26. On Android 12 and later in an Expo build that links Canvas's native
 * capture module, it is that module's capture frost where a capture plane is ready (an overlay outlet, a bridged Modal),
 * and a surface in the page, which has none, resolves its solid skin; otherwise (Expo Go, an app that excludes
 * the module, or Android 11 and earlier, where it captures nothing) it is expo-blur's frost on
 * expo-blur's releases before 57, in the page as in an overlay, and from 57 the surface
 * resolves solid. A `brand` paints brand-tinted glass and a `tint` a wash.
 *
 * Where its material resolves solid (in solid mode, under Reduce Transparency or Increase
 * Contrast, where an optional peer is missing, a browser lacks a backdrop filter or an
 * Android surface that needs a capture plane has none) it renders the plain box: the skin's
 * `style` untouched, with the contrasting `foreground` border under Increase Contrast. Under
 * glass the fill gives way to the material and a resting border becomes padding, so the
 * material covers the surface's whole solid footprint; a `stateBorder` stays over it.
 *
 * Accessibility: its root is the one node it adds, carrying only the `role`, its `accessibilityLabel`, the
 * `testID` and the accessibility-escape handler it is given, the same in solid, glass and every rung of the
 * accessibility ladder, so a screen reader and the keyboard meet its children as they would
 * in a plain View: it takes no focus stop and adds no name beyond the one it is given. Its material is hidden from
 * VoiceOver and TalkBack (`accessibilityElementsHidden`, `importantForAccessibility`
 * `no-hide-descendants`) and on the web is a set of empty, pointer-transparent boxes with no
 * role or text. Every touch passes through the material to the children and their hit slop,
 * a borderless Android ripple inside it draws in front of the frost, and a mode switch never
 * remounts the children, so their focus, input values and scroll survive it.
 *
 * This is the web host, and the host of a platform with no file of its own.
 */
export declare function GlassSurface(props: GlassSurfaceProps): import("react").JSX.Element;
//# sourceMappingURL=glass-surface.d.ts.map