This record changed while you were reviewing it
No changes were applied. Review the current version before choosing a legal recovery action.
You reviewed
Outstanding balance: $5,000
Current
Outstanding balance: $2,500
<forma-conflict-review>
Explains an optimistic-concurrency conflict, shows what changed, and offers only application-supplied recovery actions.
<forma-conflict-review>patterns/conflict-review.htmlA conflict review appears when the user tried to change a record that someone else changed first. Forma composes a bordered article with a header (a Conflict Status lozenge, a heading and an explanation), an embedded Diff viewer comparing what the user reviewed with what is current, and a footer of recovery actions. The application or Ordo detects the conflict, supplies both versions, and decides which recovery actions are legal; Forma never merges or chooses a winner.
The smallest correct markup: the canonical pattern from patterns/conflict-review.html inside its public tag. Copy this first, then adapt labels, names and state.
Rendered from the canonical pattern file.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
No changes were applied. Review the current version before choosing a legal recovery action.
Outstanding balance: $5,000
Outstanding balance: $2,500
<forma-conflict-review class="forma-component-tag">
<article class="forma-conflict-review" aria-labelledby="conflict-title">
<header class="forma-conflict-review__header">
<span class="forma-status-lozenge" data-state="attention">Conflict</span>
<h3 id="conflict-title">This record changed while you were reviewing it</h3>
<p>No changes were applied. Review the current version before choosing a legal recovery action.</p>
</header>
<div class="forma-diff-viewer">
<div class="forma-diff-viewer__grid">
<section class="forma-diff-viewer__side"><h4>You reviewed</h4><p>Outstanding balance: $5,000</p></section>
<section class="forma-diff-viewer__side"><h4>Current</h4><p>Outstanding balance: $2,500</p></section>
</div>
</div>
<footer class="forma-conflict-review__actions">
<button type="button">Reload current</button>
<button type="button">Cancel</button>
</footer>
</article>
</forma-conflict-review>
Click or tap the code once to select all of it, then copy.
A vendor record where two of three fields changed. Each side is a Diff viewer column with forma-diff-row entries, and data-change="changed" marks the rows that differ. The application offers three legal recoveries.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
Your edit to the payment terms was not saved. Compare the versions, then choose how to continue.
<forma-conflict-review class="forma-component-tag">
<article class="forma-conflict-review" aria-labelledby="conflict-review-multiple-fields-title">
<header class="forma-conflict-review__header">
<span class="forma-status-lozenge" data-state="attention">Conflict</span>
<h3 id="conflict-review-multiple-fields-title">Vendor Northwind Traders was changed by Priya Shah</h3>
<p>Your edit to the payment terms was not saved. Compare the versions, then choose how to continue.</p>
</header>
<div class="forma-diff-viewer">
<div class="forma-diff-viewer__grid">
<section class="forma-diff-viewer__side" aria-label="Version you edited">
<h4>You edited (version 7)</h4>
<dl>
<div class="forma-diff-row" data-change="changed"><dt>Payment terms</dt><dd>Net 30</dd></div>
<div class="forma-diff-row" data-change="changed"><dt>Remit-to address</dt><dd>12 Harbor Rd</dd></div>
<div class="forma-diff-row"><dt>Currency</dt><dd>USD</dd></div>
</dl>
</section>
<section class="forma-diff-viewer__side" aria-label="Current version">
<h4>Current (version 8)</h4>
<dl>
<div class="forma-diff-row" data-change="changed"><dt>Payment terms</dt><dd>Net 45</dd></div>
<div class="forma-diff-row" data-change="changed"><dt>Remit-to address</dt><dd>PO Box 88</dd></div>
<div class="forma-diff-row"><dt>Currency</dt><dd>USD</dd></div>
</dl>
</section>
</div>
</div>
<footer class="forma-conflict-review__actions">
<button type="button">Reapply my change to version 8</button>
<button type="button">Keep current version</button>
<button type="button">Cancel</button>
</footer>
</article>
</forma-conflict-review>
Click or tap the code once to select all of it, then copy.
There is no current version to compare, so the diff is omitted. The header explains what happened and the only actions are ones that cannot overwrite anything.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
Your changes were not saved. You can copy them into a new claim.
<forma-conflict-review class="forma-component-tag">
<article class="forma-conflict-review" aria-labelledby="conflict-review-record-deleted-title">
<header class="forma-conflict-review__header">
<span class="forma-status-lozenge" data-state="blocked">Conflict: deleted</span>
<h3 id="conflict-review-record-deleted-title">This expense claim was deleted while you were editing it</h3>
<p>Your changes were not saved. You can copy them into a new claim.</p>
</header>
<footer class="forma-conflict-review__actions">
<button type="button">Start a new claim with my changes</button>
<button type="button">Discard my changes</button>
</footer>
</article>
</forma-conflict-review>
Click or tap the code once to select all of it, then copy.
Each mobile example renders in its own document inside a real narrow viewport, so Forma's media and container queries run exactly as they would on a phone. Choose a width to compare.
A single-field conflict at phone width.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
<forma-conflict-review class="forma-component-tag">
<article class="forma-conflict-review" aria-labelledby="conflict-review-mobile-balance-conflict-title">
<header class="forma-conflict-review__header">
<span class="forma-status-lozenge" data-state="attention">Conflict</span>
<h3 id="conflict-review-mobile-balance-conflict-title">The balance changed while you were reviewing it</h3>
<p>No write-off was applied.</p>
</header>
<div class="forma-diff-viewer">
<div class="forma-diff-viewer__grid">
<section class="forma-diff-viewer__side" aria-label="Version you reviewed">
<h4>You reviewed</h4>
<dl><div class="forma-diff-row" data-change="changed"><dt>Outstanding balance</dt><dd>5,000.00</dd></div></dl>
</section>
<section class="forma-diff-viewer__side" aria-label="Current version">
<h4>Current</h4>
<dl><div class="forma-diff-row" data-change="changed"><dt>Outstanding balance</dt><dd>2,500.00</dd></div></dl>
</section>
</div>
</div>
<footer class="forma-conflict-review__actions">
<button type="button">Reload current</button>
<button type="button">Cancel</button>
</footer>
</article>
</forma-conflict-review>
Click or tap the code once to select all of it, then copy.
The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
Forma components have no JavaScript API. Their public contract is the markup: native elements and attributes you write, and the CSS hooks below. The CSS hook table is generated from the built stylesheet, so it always matches the shipped implementation.
| Attribute | On | Values | Default | Description |
|---|---|---|---|---|
aria-labelledby | article.forma-conflict-review | id of the header heading | — | Names the article from its heading. |
aria-label | .forma-diff-viewer__side | string | — | Names each side of the comparison (the version reviewed and the current version). |
data-state | .forma-status-lozenge | attention | blocked | — | Glyph for the conflict lozenge. |
data-change | .forma-diff-row | changed | absent | Marks a row whose value differs between versions. See Diff viewer. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-conflict-review | Block class | — | Root article with a functional border. An embedded diff viewer loses its own inline borders so the two frames do not double up. |
.forma-conflict-review__actions | Element class | — | Footer row of application-supplied actions: wrapping, end-aligned, with a top rule. |
.forma-conflict-review__header | Element class | — | Padded header with a bottom rule, holding the lozenge, heading and explanation. |
| Keys | Result |
|---|---|
| Tab / Shift+Tab | Moves through the recovery actions. The comparison itself is static content. |
| Enter / Space | Activates the focused action (native button behavior). |
| Event | Description |
|---|---|
click | Native click on recovery buttons. The application or Ordo performs the chosen recovery. |
Not a form control. If the actions are form submit buttons, the application still validates legality server-side.
| State | How it is expressed | Presentation |
|---|---|---|
| Conflict with comparison | header, diff viewer and actions | Both versions are available and differences are marked. |
| Conflict without comparison | header and actions, no diff viewer | The current version is missing or cannot be shown; the header explains why. |
| Changed row | data-change="changed" on .forma-diff-row | Thick inline-start border beside rows that differ. |
Generated fault-injection specimens expose content, spacing, color-cue, and reduced-effective-contrast risks. They screen presentation robustness as engineering screens without claiming human-subject validation.