Skip to content
Draft
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion docs/specs/AST-082-native-first-surfaces/spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -505,7 +505,19 @@ props (DEC-6) carry behavior and presentation choices a platform offers, not
visuals.

Rejected: visual props for one platform on components, because they move a
theme decision into every call site.
theme decision into every call site. Amended: `Button` and `IconButton`'s
`surface` prop is the one exception.
Comment thread
astracat-bot[bot] marked this conversation as resolved.
Resolved

Amended 2026-11-18 (**Decider:** `cixzhang`, `2026-11-18 13:08 PT`): `Button` and
`IconButton` take a per-call-site `surface` prop (`plain` default, or `glass`) as a
Comment thread
astracat-bot[bot] marked this conversation as resolved.
Resolved
situational appearance choice. It is a platform prop in the iOS and Android
Comment thread
astracat-bot[bot] marked this conversation as resolved.
Resolved
contracts (FR3, FR5); the core and web contracts do not have it. An explicit
`surface` decides that Button or IconButton's look. When `surface` is unset, the
theme's native `material` intent and the platform's placement rule decide it.
Where a platform or OS version has no system glass, `glass` draws that
platform's chrome material, as the platform's record defines; Reduce
Transparency and Increase Contrast apply as for any glass. Every other
native-only look stays theme intent (OQ7).

### DEC-3 — How a native platform is built is decided by measurement

Expand Down Expand Up @@ -733,3 +745,6 @@ would need the same words again.
`aria-*` or `data-*` input still type-checks. Options: a lint rule, a
development warning with the input not applied, or both. Recommendation: both,
with the runtime change shipped as a breaking change under FR14.
- **OQ7 — Which other surfaces take surface-specific props, and where do they
live in the contracts?** (`human-api`) DEC-2 names `Button` and `IconButton`'s
`surface` prop as the one exception to theme-owned native looks.
3 changes: 2 additions & 1 deletion docs/specs/AST-093-native-component-guidelines/spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,8 @@ validating, and reviewing individual native components while
`defineTheme` definition (`spec:AST-082/FR18`) and native intent and platform
entries from `defineNativeTheme` (`spec:AST-082/FR10`). A component reads
every such value from the theme, never hard-codes one, and never adds a
visual prop for one platform (`spec:AST-082/DEC-2`). Each spec lists the
visual prop for one platform, except `Button` and `IconButton`'s `surface`
Comment thread
astracat-bot[bot] marked this conversation as resolved.
Resolved
prop (`spec:AST-082/DEC-2`). Each spec lists the
theme values the component reads.
- **FR5 — Every native component is tested and validated the same way.** A
change to a native component ships with:
Expand Down