Mobile reference
Every Forma component has at least one explicit mobile example rendered in a real narrow viewport, plus a 320px baseline. This index links straight to each one with the first thing that changes at narrow widths.
The mobile contract
- No page-level horizontal scrolling at 320 CSS pixels and wider; wide data scrolls inside a labelled, keyboard-reachable region.
- Standalone touch targets are approximately 44 by 44 CSS pixels where practical.
- Layouts stack, wrap or collapse without changing semantic order or meaning.
- No hover-only, drag-only or pointer-only interaction.
See the Mobile settings composition for independent controls working together on a phone.
Actions
-
Button · Wrapping action row on a phone
<forma-button>forma-actionsis a wrapping flex row: buttons that do not fit move to the next line in source order. -
Command group · Record commands on a phone
<forma-command-group>forma-command-group__commandsis a wrapping flex row, so commands move to new lines in source order instead of shrinking below 44px. -
Mobile action bar · Sticky under a long form
<forma-mobile-action-bar>At 40rem (640px) and below the bar is
position: sticky; inset-block-end: 0with a z-index above the content, so it stays visible while its container scrolls. -
Overflow command disclosure · Overflow on a phone
<forma-overflow-command-disclosure>The summary row is at least 44px tall and spans the available width, so it is an easy tap target.
Form inputs
-
Checkbox · Mobile filter list
<forma-checkbox>The box column is a fixed 1.25rem; the text column takes the remaining width and wraps long labels.
-
Combobox · Mobile assignee field
<forma-combobox>The label, control and help stack in one column and the input fills the width with a 44px minimum height.
-
Date and time field · Mobile delivery booking
<forma-date-time-field>The two fields sit side by side when there is room and stack into one column on a phone, because the enclosing grid uses
minmax(min(100%, 16rem), 1fr)tracks. -
Date range · Mobile activity filter
<forma-date-range>At 40rem (640px) and below the fields grid becomes one column and the → separator is hidden, so each date input gets the full width.
-
File upload queue · Mobile evidence upload
<forma-file-upload>At 40rem (640px) and below each queue row becomes one column: file name and size, then the progress bar, then the status or a full-width action button.
-
Form · Mobile mission customer
<forma-form>The auto-fit form row becomes one column from available container width, not device detection.
-
Numeric stepper · Mobile order quantities
<forma-numeric-stepper>Inputs stay at most 10rem wide at every width, so the narrow field keeps signalling a short number.
-
Range entry · Mobile age range
<forma-range-entry>At 44rem (704px) and below the inputs grid becomes one column: Minimum, the separator word, then Maximum.
-
Rule builder · Mobile audience rule
<forma-rule-builder>At 44rem (704px) and below each clause becomes one column: Field, Operator, Value and Remove stack in source order.
-
Search · Mobile document search
<forma-search>At 30rem (480px) and below the control becomes one column: the input takes the full width and the Clear button sits beneath it.
-
Select · Mobile country picker
<forma-select>The select fills the available width and keeps a 44px minimum height; the indicator stays pinned 1rem from the inline end.
-
Slider · Mobile display brightness
<forma-slider>The input is full width with a 44px minimum height, so the thumb and track are comfortable touch targets.
-
Switch · Mobile settings list
<forma-switch>The track keeps its fixed 2.75rem width; the text column takes the remaining width and wraps long labels onto several lines.
-
Text field · Mobile contact details
<forma-text-field>Inputs are
inline-size: 100%of their column, so fields fill the phone width and never overflow horizontally. -
Textarea · Mobile feedback form
<forma-textarea>The textarea fills the phone width;
max-inline-size: 100%stops the resize handle from widening it past the screen.
Selection and choice
-
Choice group · Long options on a phone
<forma-choice-group>Cards are full-width grid rows; text wraps inside the card and the card grows in height, so nothing overflows at 320px.
-
Hierarchical choice · Nested tree on a phone
<forma-hierarchical-choice>At 44rem and below nested lists indent by 0.75rem and branches by 0.5rem (instead of 1.25rem and 0.75rem), so three levels still fit at 320px.
-
Hierarchical multi-choice · Notification areas on a phone
<forma-hierarchical-multi-choice>At 44rem and below nested indentation shrinks to 0.75rem and branch padding to 0.5rem so item text keeps most of the width.
-
Image choice · Stacked media on a phone
<forma-image-choice>At 44rem and below
forma-choice--mediaswitches to one column: the 4:3 media frame spans the card width above the label and description. -
Multi-choice · Between-two-and-four rule on a phone
<forma-multi-choice>Guidance, option cards and the status line stack in one column and wrap long text; nothing scrolls horizontally at 320px.
-
Segmented control · Wrapping segments on a phone
<forma-segmented-control>At 44rem and below
forma-segmentedtakes the full inline size and each segment flexes from amin(10rem, 100%)basis, so segments share the width evenly.
Assessment and survey
-
Allocation · Allocation on a phone
<forma-allocation>Each item switches from a label/field row to a single column: label on top, input full width underneath.
-
Best–Worst · Best–Worst on a phone
<forma-best-worst>The header row (Option, Best, Worst) is hidden below 44rem, so the description must state the column order in text.
-
Binary choice · Agree or disagree on a phone
<forma-binary-choice>The options switch from a side-by-side inline grid to a single column that fills the width.
-
Ordinal scale · Seven-point agreement on a phone
<forma-ordinal-scale>Below 44rem every cardinality collapses to one column; each option becomes a 52px-tall row with the marker at the start and the label beside it.
-
Pairwise choice · Stacked comparison on a phone
<forma-pairwise-choice>The three-column grid becomes one column: Option A, the "or" separator, then Option B, preserving source order.
-
Question shell · Question on a phone
<forma-question>The header grid keeps the number in an auto column and gives the prompt the remaining width, so long prompts wrap instead of overflowing.
-
Ranking · Ranking on a phone
<forma-ranking>Each row becomes a two-column grid (position, label); the actions move to their own full-width line beneath.
-
Semantic differential · Endpoint key on a phone
<forma-semantic-differential>Below 44rem the aria-hidden endpoint row is hidden and the
--mobilekey, which states which number means what, is shown under the scale. -
Single-choice matrix · Matrix decomposed on a phone
<forma-matrix-single>Below 44rem the row grid becomes one column: the row prompt sits above its choices.
-
Special choice · Several special answers on a phone
<forma-special-choice>.forma-special-choicesis a wrapping flex row, so pills move to the next line instead of shrinking. -
Survey progress · Long section name on a phone
<forma-survey-progress>The header is a wrapping flex row: when label and value do not fit side by side, the value drops to its own line.
-
Symbol rating · Ten-point rating wrapping on a phone
<forma-symbol-rating>The options row is an inline flex container with wrapping, so symbols continue on a second line when the width runs out.
Navigation
-
Hierarchy tree · Deep tree on a phone
<forma-hierarchy-tree>Below 30rem each nested list indents by 0.5rem instead of 1rem, so four levels cost 1.5rem rather than 3rem of width.
-
Navigation shell · Compact navigation on a phone
<forma-navigation-shell>At 48rem and below the grid becomes one column, the persistent nav is removed with display: none and the compact details is shown.
-
Pagination · Compact pagination on a phone
<forma-pagination>Page links other than the current one are hidden below 40rem; the current page stays as the anchor between Previous and Next.
-
Scope trail · Scope trail on a phone
<forma-scope-trail>The list is a wrapping flex row, so items continue on new lines instead of truncating or scrolling.
-
Skip link · Translated skip link on a phone
<forma-skip-link>Position is fixed relative to the viewport, so the link appears in the top inline-start corner even when the page is scrolled.
-
Tabs · Tabs on a phone
<forma-tabs>Tabs never wrap onto a second row;
.forma-tabs__listscrolls horizontally inside its own bounds when they overflow. -
Wizard · Wizard on a phone
<forma-wizard>The header becomes one column: position and title first, then a full-width progress bar.
Feedback and status
-
Alert · Mobile review prompt
<forma-alert>Below 40rem the grid becomes a single column: icon, then text, then the action.
-
Conflict review · Mobile balance conflict
<forma-conflict-review>Below 40rem the diff viewer's two sides stack: the version you reviewed above the current version.
-
Empty state · Mobile filtered list
<forma-empty-state>Vertical padding scales with
clamp(2rem, 8vw, 5rem), so the block is compact on phones and roomier on desktops. -
Freshness · Mobile scan age
<forma-freshness>The line is a wrapping flex row: label, time and state move onto new lines when they do not fit.
-
Obligation panel · Mobile finalization
<forma-obligation-panel>Below 44rem the header stacks: heading and explanation first, then the count.
-
Operation status · Mobile unknown outcome
<forma-operation-status>Below 40rem the three-column grid becomes one column: symbol, text, then actions.
-
Progress bar · Mobile backup
<forma-progress-bar>The header is a wrapping flex row: when label and value do not fit on one line, the value moves below the label.
-
Readiness checklist · Mobile month-end close
<forma-readiness-checklist>Items keep their three columns (glyph, label, action) at every width; the label column shrinks and wraps.
-
Scroll progress · Mobile release notes
<forma-scroll-progress>The bar is 0.1875rem (3px) tall and spans the article's full width at every screen size.
-
Skeleton · Mobile message list
<forma-skeleton>Lines are percentage widths (100%, 72% short, 55% title), so they scale with the screen instead of overflowing.
-
Spinner · Mobile long label
<forma-spinner>The spinner is inline-flex: the 1.25rem ring keeps its size and the label wraps beside it.
-
Start-up screen · Phone start-up
<forma-startup>The identity, status and actions stack in one centered column capped at 36rem, so nothing scrolls sideways at 320 pixels.
-
State survivability · Mobile sync states
<forma-state-survivability>Below 30rem each row becomes a single column: the lozenge sits above its explanation.
-
Status lozenge · Mobile status set
<forma-status-lozenge>Below 30rem each lozenge in a set takes the full row and its content is centered, so the set becomes a vertical list.
-
Toast · Mobile draft saved
<forma-toast>The toast width is capped at
min(26rem, 100vw - 2rem), so at 320px it fills the width with a 1rem margin on each side. -
Validation message · Mobile long message
<forma-validation-message>The message is a flex row: the 1.5rem mark keeps its size and the text wraps in the remaining width.
-
Validation summary · Mobile survey page
<forma-validation-summary>The two-column grid keeps the mark in a narrow first column; the heading and list take the remaining width and wrap.
Faults and recovery
-
Diagnostic status · Queued reports on a phone
<forma-diagnostic-status>The status is inline-flex and limited to 100% of its container, so on a phone it becomes as wide as the screen allows and the text column wraps.
-
Fault · Long title and reference on a phone
<forma-fault>Below 36rem the three-column grid becomes two columns (marker and body); the recovery region moves to its own full-width row underneath, keeping source reading order.
-
Fault banner · Diagnostics banner on a phone
<forma-fault-banner>Below 36rem the three-column grid (icon, body, actions) becomes two columns; the recovery group moves to its own full-width row beneath the body without changing reading order.
-
Fault blocking · Blocking fault on a phone
<forma-fault-blocking>Below 36rem the dialog is the viewport width minus 1rem and at most the dynamic viewport height minus 1rem, so it never extends under browser toolbars.
-
Fault details · Stacked values on a phone
<forma-fault-details>Below 36rem each term/value pair stacks into one column with the value directly under its term.
-
Fault inline · Upload failure on a phone
<forma-fault-inline>Below 36rem the marker and body share the first row and the recovery group moves to a full-width row underneath.
-
Fault notification · Sync failure on a phone
<forma-fault-notification>The surface is fixed to the bottom inline-end corner with a 1rem inset (respecting the safe-area inset) and is at most the viewport width minus 2rem, so it never causes horizontal scrolling.
-
Fault reference · Long reference on a phone
<forma-fault-reference>The row wraps: the label, code and button flow onto separate lines when they do not fit, instead of overflowing.
-
Fault summary · Fault summary on a phone
<forma-fault-summary>The summary is a single-column grid at every width; the marker and heading stay side by side and the heading text wraps.
-
Recovery actions · Stacked actions on a phone
<forma-recovery-actions>Below 36rem the group takes the full width and each button becomes a full-width row (flex-basis 100%).
Overlays and disclosure
-
Action menu · Record menu on a phone
<forma-menu>At 44rem and below the menu may grow to
100vw - 1remwide and100dvh - 1remtall; its minimum width staysmin(14rem, 100vw - 2rem). -
Dialog · Short form on a phone
<forma-dialog>At 44rem and below the dialog is
100vw - 1remwide and at most100dvh - 1remtall, so it fits phones in portrait and landscape and follows the dynamic viewport as browser toolbars appear. -
Disclosure · Long summary on a phone
<forma-disclosure>The summary is a flex row: the text wraps onto several lines while the + / × indicator stays at the inline end.
-
Flyout · Record detail on a phone
<forma-flyout>Width is
min(28rem, 90vw): at 320px the panel is 288px wide and a 32px strip of the dimmed page stays visible on the opposite side. -
Overview disclosure · Stale evidence on a phone
<forma-overview-disclosure>The section is a single-column grid at every width, so the overview is always first in reading order and on screen.
-
Popover · Field help on a phone
<forma-popover>At 44rem and below the surface is at most
100vw - 1remwide and100dvh - 1remtall, so it never causes horizontal scrolling at 320px. -
Tooltip / contextual hint · Hint at the edge of a phone screen
<forma-tooltip>The trigger stays a 44 by 44px tap target at every width; tapping it opens the hint (popovertarget), and tapping elsewhere closes it. Hover is never required.
Layout primitives
-
Bounded overflow · Mobile table scroll
<forma-bounded-overflow>The region is
max-inline-size: 100%, so it is never wider than the screen; the table scrolls inside it with a swipe. -
Cluster · Mobile toolbar
<forma-cluster>At 320px the buttons no longer fit on one row, so the last ones wrap onto a second line in source order.
-
Container · Mobile page width
<forma-container>All presets are at least 45rem, so on phones
min(100%, …)makes every container full width. -
Form row · Stacked on a phone
<forma-form-row>Below twice the column minimum the row has one column, so each field is a full-width block in source order.
-
Frame · Mobile article image
<forma-frame>The frame is as wide as its parent, so at 320px the image is 320px minus the page gutter and its height follows the 4 / 3 ratio.
-
Grid · Mobile environment list
<forma-grid>With the default 16rem minimum, 320px and 390px screens fit only one track, so items stack in source order.
-
Landmark region · Mobile wrapped band
<forma-landmark-region>At 48rem and below the region becomes
position: static, so it scrolls away instead of permanently covering part of a short screen. -
Measure · Mobile reading width
<forma-measure>On phones the available width is less than 65ch, so
min(100%, 65ch)resolves to the full width. -
Mosaic · Mobile single column
<forma-mosaic>At 30rem and below the grid has one column and
data-spanitems are reset togrid-column: auto. -
Priority stack · Mobile stacked priority
<forma-priority-stack>At 30rem and below
--forma-priority-minbecomes 100%, so each region takes its own full-width row. -
Rail · Mobile collapsed rail
<forma-rail>At 48rem viewport width and below the grid has a single
minmax(0, 1fr)column for both start and end rails. -
Responsive grid · Mobile collapsed span
<forma-responsive-grid>At 48rem and below
forma-span-2becomesgrid-column: 1 / -1, so the primary region never forces a second track. -
Section · Mobile marketing sections
<forma-section>Inside
.forma-sitesection spacing comes from fluid tokens, so padding and band margins are smaller at 320px than on desktop. -
Sidebar · Mobile filters above results
<forma-sidebar>At 30rem and below the sidebar switches to a one-column grid and both regions take the full width.
-
Split · Mobile wrapped split
<forma-split>Below roughly 44rem of available width the supporting region wraps onto its own line and both regions become full width.
-
Stack · Mobile account summary
<forma-stack>A stack is one column at every width, so there is no breakpoint and nothing moves at 320px.
-
Surface · Mobile panel
<forma-surface>The surface is as wide as its parent; padding stays at 1.5rem on every side, leaving the rest for content.
-
Switcher · Mobile stacked regions
<forma-switcher>Below roughly 45rem of available width (28rem + 16rem + gap) the regions wrap and each takes the full width.
Workspaces and shells
-
Application identity · Compact phone header, mark only
<forma-app-identity>The link keeps a 44 pixel minimum height, so the mark is a full-size touch target even at 24 pixels.
-
Dashboard grid · Mobile single column
<forma-dashboard-grid>At 40rem and below the grid is one
1frcolumn;forma-span-2andforma-span-fullchildren simply fill that column. -
Focus stage · Mobile stacked support
<forma-focus-stage>At 48rem and below the stage is a single
minmax(0, 1fr)column; the 14rem support minimum no longer applies and nothing overflows at 320px. -
Master/detail workspace · Mobile record switcher
<forma-master-detail>At 40rem and below the grid becomes one column; the list turns into a horizontal row of 12rem-wide links that scrolls inside itself, so the page never scrolls sideways at 320px.
-
Preview surface · Mobile invoice preview
<forma-preview-surface>At 40rem and below the header and footer switch to a stretched column, so the title, controls, status and action each take the full width.
-
Record header · Mobile record with collapsed actions
<forma-record-header>At 40rem and below the header is one column: breadcrumbs, type, identifier, status and context first, then actions.
-
Resizable split pane · Mobile without a separator
<forma-resizable-split-pane>At 48rem and below the grid becomes a single column and
.forma-split-pane__separatorisdisplay: none, so it leaves the tab order and the accessibility tree. -
Split pane · Mobile reading order
<forma-split-pane>At 48rem and below the grid becomes a single
minmax(0, 1fr)column; the 16rem secondary minimum no longer applies, so nothing overflows at 320px. -
Workspace shell · Mobile stacked regions
<forma-workspace-shell>At 48rem and below the named grid collapses to one column; every region takes the full width and nothing scrolls horizontally at 320px.
Data display
-
Active filter summary · Mobile summary with many filters
<forma-active-filter-summary>Filters wrap onto as many rows as needed; the list never scrolls horizontally at 320px.
-
Collection toolbar · Mobile collection toolbar
<forma-collection-toolbar>At 40rem (640px) and below the grid becomes
1fr auto: search and the controls each span the full width, and the count sits beside the remaining space. -
Comparison grid · Mobile release comparison
<forma-comparison-grid>The grid never recomposes. When the table is wider than the screen the region scrolls horizontally inside itself and the page does not overflow at 320px.
-
Comparison pairs · Mobile plan change
<forma-comparison-pairs>At 30rem (480px) and below each item switches to a single column: label, first value, second value, in DOM order.
-
Data grid · Mobile record projection
<forma-data-grid>At 30rem (480px) and below the table, rows and cells switch to block display;
theadis hidden and everytdshows itsdata-labelin a 6.5rem label column beside the value. -
Dense ledger · Mobile ledger with contained scroll
<forma-dense-ledger>The ledger never recomposes. Below its natural width the
.forma-bounded-overflowregion scrolls horizontally, so the page itself has no horizontal overflow at 320px. -
Diff viewer · Mobile stacked comparison
<forma-diff-viewer>At 40rem (640px) and below the grid becomes one column; the second side gets a top rule instead of a side rule.
-
Evidence relationship · Mobile evidence relationship
<forma-evidence-relationship>The component is a single-column grid at every width, so there are no breakpoints.
-
Feed item · Mobile feed item
<forma-feed-item>At 30rem (480px) and below the grid becomes a single
minmax(0, 1fr)column and.forma-feed-item__metaaligns to the start under the title. -
Identifier & critical value · Mobile execution reference
<forma-identifier>Long identifiers break at any character (
overflow-wrap: anywhere), so a 30-character ID wraps at 320px instead of overflowing. -
Key-value list · Mobile account summary
<forma-key-value-list>At 30rem (480px) and below each row switches to
grid-template-columns: 1frwith a 0.25rem gap: the label sits directly above its value. -
Metric card · Mobile metric stack
<forma-metric-card>The value size follows
clamp(2rem, 8vw, 3.5rem): about 2rem at 320px and 390px, reaching 3.5rem only at wide viewports. -
Metric value change · Mobile updated metric
<forma-metric-value-change>The tint is background color only; no position, size or opacity changes, so nothing shifts on a small screen.
-
Path summary · Mobile data flow path
<forma-path-summary>No breakpoints: the numbered list keeps its 1.5rem gutter and every step wraps within the remaining width.
-
Provenance trail · Mobile provenance trail
<forma-provenance-trail>The trail has no breakpoints: each stage keeps a 2rem inline-start gutter for the marker and connector, and text wraps in the remaining width.
-
Relationship index · Mobile relationship index
<forma-relationship-index>At 30rem (480px) and below each row becomes one column with a 0.25rem gap: relationship type, then targets.
-
Reorder states · Mobile drag in progress
<forma-reorder-states>At 44rem and below each ranking item stacks: position and label on the first row, move buttons in a full-width two-column row below, so the non-drag path keeps 2.75rem touch targets.
-
Timeline · Mobile activity history
<forma-timeline>The timeline is already single-column: a fixed 1.25rem marker column beside a
minmax(0, 1fr)content column, so it needs no breakpoint. -
Work queue · Mobile work queue
<forma-work-queue>At 40rem (640px) and below each item becomes a single column and its button stretches to 100% width, giving a full-width touch target.
Workflow and diagrams
-
Diagram · Mobile scrolling canvas
<forma-diagram>The canvas keeps its consumer-supplied size (here 560 by 150 px) and scrolls inside
.forma-diagram__viewport; the page itself does not scroll sideways at 320px. -
Lane board · Mobile scrolling lanes
<forma-lane-board>Lanes are
min(18rem, 85vw)wide, so at 320px each lane is about 272px and the edge of the next lane is visible as a scroll cue. -
Spatial canvas · Mobile map with object index
<forma-spatial-canvas>The surface keeps its 48rem minimum width and scrolls inside
.forma-spatial-canvas__viewport; the page does not scroll sideways at 320px.
Command and keyboard-first
-
Character grid · Contained node list on a phone
<forma-character-grid>The grid keeps its 60 columns; the viewport scrolls horizontally inside its border and the page itself never scrolls sideways.
-
Character grid 3270 profile · 3270 menu on a phone
<forma-character-grid-3270>An 80-column 3270 screen is wider than any phone in portrait, so the viewport scrolls horizontally inside its border; the page never does.
-
Character grid field · Payment entry on a phone
<forma-character-grid-field>Below 40rem the row pitch becomes 2.75rem, so each field is a 44px-tall target; field widths stay tied to their cells.
-
Character grid keys · Key bar on a phone
<forma-character-grid-keys>Phones have no F-keys, so the presented buttons are the only way to trigger PF actions there; keep every action on screen.
-
Character grid reveal · Sign-on banner on a phone
<forma-character-grid-reveal>Timing derives from cell coordinates and grid geometry, so a narrow viewport neither speeds up nor slows down the reveal.
-
Character grid selection · Option column on a phone
<forma-character-grid-selection>At the touch pitch the one-cell field grows to 2.75rem, which fits because the Opt column plus its gutter is five cells (CG-17).
-
Character grid status · Status line on a phone
<forma-character-grid-status>Messages wrap inside their reserved rows at any width; at the 44px touch pitch each row is taller, so reserved rows hold the same text.
-
Character grid workflow · Service error on a phone
<forma-character-grid-workflow>Each 80-column screen scrolls horizontally inside its own named viewport; the page scrolls only vertically between screens.
-
Command palette · Full-screen palette on a phone
<forma-command-palette>Below 40rem the dialog becomes 100vw by 100dvh with no border, so the on-screen keyboard and the results share the full screen.
Human–agent interaction
-
Composer · Mobile capture
<forma-composer>At 40rem and below the actions row becomes a stretched column: input methods as a two-column grid of equal buttons, then a full-width submit button.
-
Conversation · Mobile history
<forma-conversation>At 40rem and below each turn is a single column: speaker label, then content, then actions.
-
Handoff summary · Mobile approval
<forma-handoff-summary>At 30rem and below each fact row becomes one column with a small gap: label, then value.
-
Understanding review · Mobile review with a question
<forma-understanding>At 40rem and below the header stacks its text above the status lozenge, stretched to the full width.
Attention and verification
-
Attention path · Mobile review path
<forma-attention-path>The supporting grid uses
minmax(min(100%, 15rem), 1fr), so below about 31rem it is a single column in step order. -
Emphasis budget · Mobile decision
<forma-emphasis-budget>The support grid uses
minmax(min(100%, 15rem), 1fr), so supporting regions stack into one column on phones. -
Verification frame · Mobile case closure
<forma-verification-frame>The facts grid uses
minmax(min(100%, 12rem), 1fr), so at 320px each fact takes a full row.
Security posture
-
Security blockers · Blockers on a phone
<forma-security-blockers>The list is a single-column grid at every width; each entry's explanation is a block under its ID link.
-
Security evidence age · Evidence freshness on a phone
<forma-security-evidence-age>The list is a single-column grid at every width, so entries stack vertically with a 0.5rem gap.
-
Security evidence chain · Evidence chain on a phone
<forma-security-evidence-chain>Below 30rem the steps stack in a single column, preserving the Source → Observation → Invariant → State order top to bottom.
-
Security exception · Active exception on a phone
<forma-security-exception>The description list auto-fits columns of at least
min(12rem, 100%), so at 320px every term/value pair stacks in one column. -
Security invariant result · Violated invariant on a phone
<forma-security-invariant-result>The header wraps: the eyebrow takes a full line, then the ID and the state word share a line or wrap onto two when space runs out.
-
Security posture · Blocked posture on a phone
<forma-security-posture>Below 30rem the header switches from a wrapping flex row to a single-column grid, so the status label sits under the heading instead of beside it.
-
Security state matrix · State counts on a phone
<forma-security-state-matrix>Tiles auto-fit columns of at least 7rem, so at 320px they form two columns and wrap onto three rows; the source order Verified, Violated, Unknown, Stale, N/A reads left to right, top to bottom.
-
Security trend · Security trend on a phone
<forma-security-trend>Entries stack in a single-column grid at every width, with the direction word on its own line above the explanation.
-
Security unknown · Unknown effect on a phone
<forma-security-unknown>The description list auto-fits columns of at least
min(12rem, 100%), so at 320px each term/value pair stacks in one column.
Site and editorial
-
Badge · Phone topic links
<forma-badge>The badge list wraps with a small gap, moving whole badges to the next line instead of scrolling horizontally.
-
Call to action · Phone inverse CTA
<forma-cta>Text needs at least 20rem (or the full width), so actions wrap below it on phones and start at the inline start.
-
Callout · Phone note in an article
<forma-callout>The callout is capped at the reading measure and shrinks to the column; its padding stays compact so text keeps most of the width.
-
Card grid · Phone single column
<forma-card-grid>Columns drop by content: below about two 15rem cards the grid is one column, whatever
data-forma-columnssays. -
Code sample · Phone lock file
<forma-code-sample>The block is capped at 100% of its column; long lines such as checksums scroll inside it and never cause page-level horizontal scrolling.
-
Documentation layout · Phone compact navigation
<forma-documentation-layout>Below a 48rem main-region width the layout is one column in source order: navigation, article, outline.
-
Entry index · Phone single column
<forma-entry-index>Below a 56rem list width each row regroups into a 3.5rem marker column beside the content, with heading, summary and link stacked in the second column.
-
Facts · Phone stacked facts
<forma-facts>Items fit by content with an 11rem minimum: two columns fit around 390px, and one column at 320px or with larger text.
-
Hero · Phone hero with statement
<forma-hero>The aside wraps below the content when the row cannot give the content at least 55% and the aside its minimum; there are no breakpoints.
-
Marketing shell · Phone-width frame
<forma-marketing-shell>The header is sticky only at 40rem wide and 36rem tall or more; on phones it scrolls away so it never covers focused content or reading space.
-
Prose · Phone article with long inline code
<forma-prose>The measure cap stops mattering on phones; the article takes the column width and text wraps normally.
-
Section heading · Long title with an action on a phone
<forma-section-heading>The text group needs at least 20rem (or the full width when narrower), so the aside wraps below it on phones.
-
Site footer · Phone footer with action and links
<forma-site-footer>The identity block and action group wrap into a single column; the action keeps a 44px minimum target.
-
Site header · Phone navigation wraps
<forma-site-header>Below a 56rem header width the tagline is hidden (a container query on the header), keeping navigation to about two lines.
-
Steps · Phone method
<forma-steps>The counter column keeps its minimum width and each item's text wraps beside it, so numbers stay aligned at 320px.
Utilities
-
Icon · Icon action on a narrow screen
<forma-icon>The parent button supplies the touch target while the icon remains a 1.25em decorative SVG.
-
Text roles · Hero introduction on a phone
<forma-text-roles>The lead uses
clamp(1.125rem, 0.875rem + 0.85vw, 1.5rem), so it is smallest on phones and still larger than body text. -
Visually hidden · Icon toolbar on a phone
<forma-visually-hidden>Hidden text takes no space, so icon buttons stay compact and the cluster wraps only when the buttons themselves no longer fit.