Skip to main content

Module response

Module response 

Expand description

How the shared components answer the pointer: the hover and press response, as a theme role (docs/design-language.md, “Lifts”; docs/architecture/theming.md, the response role).

A pointed-at control lifts off its ground; a pressed one presses into it. Both are four numbers a theme may set — how far the fill lifts toward the next surface step (lift), how much of the person’s accent washes into that lift (tint), how far the whole control scales about its centre (scale) and how strongly a lit edge catches it (glow) — and every shared component reads them here (crate::chrome::selection_tier_on, crate::chrome::selector_tier, a button’s face). An app never picks one: it says a control is hovered or pressed, and the theme’s response draws it.

Structs§

Response
The hover and press response of the shared components.
ResponseStep
One state’s response: the four levers a theme may move.