Cell UI
Route Cell-native UI changes to product principles, runtime contracts, evidence, and delivery status.
HEAD a63778eCell UI is a separate development surface under the shared Cell rendering and interaction model. Start with the smallest contract that answers the task.
| Read this page when | A change affects Cell UI layout, rendering, input, widgets, semantics, accessibility, or editor behavior. |
|---|---|
| First answer | Is the missing decision about product principles, runtime foundations, a widget contract, browser projection, or delivery status? |
| Boundary | Canvas rendering and Host composition remain owned by their respective architecture and Host UI routes. |
| Follow-up | Choose the smallest Cell UI route below, then follow its source and evidence links. |
| Question | Route |
|---|---|
| What are the current product facts, upstream choices, and runtime flow? | Cell UI overview |
| Which visual principles and Cell-native interaction rules apply? | Cell-native UI design and Classic Macintosh translation |
| Which generic editor contracts are shared by Cell-native editors? | Editor foundations |
| Which lifecycle, input, feedback, and primitive contracts apply? | Cell primitives |
| Which geometry, clipping, paint, hit, and invalidation rules apply? | Cell UI compositor |
| Which widget state, pointer, keyboard, scroll, or editor behavior applies? | Cell widget behavior |
| How is the Cell semantic tree projected to browser accessibility? | Cell UI semantics and Accessibility |
| How is native browser or macOS text input verified? | Native input |
| What is delivered, pending, or blocked for Cell UI? | Cell UI status |