Skip to content
Draft
Changes from 1 commit
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
11 changes: 10 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,13 @@ 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, typed from the shared contracts. Every other
Comment thread
astracat-bot[bot] marked this conversation as resolved.
Resolved
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 +739,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.