VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

The Gold Standard of Websites | Separating transform-mix() Weighted Transform Blending from transform-interpolate() Progress Mapping

transform-mix(translateX(0) 25%, translateX(40px) 75%) can produce translateX(30px). transform-interpolate(75%, 0%:translateX(0), 100%:translateX(40px)) can reach the same transform. Add a 60% stop containing rotate(45deg), or leave half the mix weight to identity, and the equality disappears.

This lesson continues The Gold Standard of Websites, the Gold Standard of Education and the How X Works hub. Every element, transform list, weight, stop, progress source and matrix observation is an original synthetic fixture. The lesson does not promise shipping support, treat transform order as commutative or infer the author’s control model from one final matrix.

Record each transform list in order, raw and normalized weights, identity remainder, progress source, stop positions, active interval, easing, matching-prefix interpolation, matrix fallback, resolved matrix, browser build and unavailable behavior.

The CSS Values and Units Module Level 5 defines transform-mix() and transform-interpolate(). The CSS Transforms Module Level 1 defines transform-list interpolation, identity extension and matrix fallback. The cited CSS Values Level 5 text is an Editor’s Draft dated 6 November 2026. It labels these facilities early exploration and warns that major breaking changes are expected. The fixtures therefore explain the current model and record unsupported syntax as unavailable; they do not promise browser support.

THE GOLD STANDARD · WEBSITES

transform-mix() blends weighted transform lists; transform-interpolate() maps progress through transform stops

The proposed transform-mix() function combines weighted transform lists, treating each list as a contribution from the identity transform and assigning any missing share to identity. The proposed transform-interpolate() function evaluates a progress source against ordered transform stops, applies stop fixup and easing and interpolates inside the active interval. Both use transform interpolation rules, but their control structures are different.

Fast route
Start with the decisive rule.
Start this route

Measurement route
Build the browser state and evidence ledger.
Start this route

Comparison route
Separate the nearest lookalikes.
Start this route

Transfer route
Change the context and retest.
Start this route

Reporting route
State limits and continue reading.
Start this route

Chapter contents

Open the full chapter index

1. Give the control distinction

transform-mix() assigns contribution weights to transform lists. transform-interpolate() places transform lists at mapping positions and evaluates one progress coordinate.

Original worked example. A 75% contribution and a 75% coordinate can produce the same translation in a two-endpoint control. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Add a middle rotation stop. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Keep contribution and coordinate ledgers separate. If this check fails, mark the claim unavailable and repair the method before continuing.

Keep grammar, payload type, normalization, active interval, interpolation rule and computed result in separate fields so equal output cannot rewrite the mechanism.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Contents · Next chapter

2. Start from identity

A transform mix combines each input relative to the identity transform. Identity is an actual neutral participant, not an empty visual assumption.

Original worked example. Half of translateX(40px) and half identity yields translateX(20px). The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Give the transform a full weight. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record the identity contribution explicitly. If this check fails, mark the claim unavailable and repair the method before continuing.

Use a positive case, a clean negative case and an unavailable case. Unavailable means the required syntax or evidence was not established.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

3. Normalize transform weights

Raw weights are normalized when their total exceeds the complete share, while a shortfall remains assigned to identity.

Original worked example. Two equally weighted lists remain equal after scaling both weights. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Double only one weight. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Save raw weights, normalized shares and identity remainder. If this check fails, mark the claim unavailable and repair the method before continuing.

Change one consequential premise while keeping the rest fixed. Predict the new branch before inspecting it and preserve disagreement.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

4. Preserve transform order

Transform lists are ordered matrix products. translate then rotate is not generally equivalent to rotate then translate.

Original worked example. Two lists contain the same functions in opposite order and yield different matrices. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Use an element centered at the origin. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Archive function order and transform origin. If this check fails, mark the claim unavailable and repair the method before continuing.

Carry one plausible alternative through the ledger, then choose the next observation that separates it from the leading account.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

5. Match transform functions where possible

Transforms Level 1 interpolates matching function prefixes directly before converting incompatible remainders to matrices.

Original worked example. translateX endpoints interpolate numerically. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Change one endpoint to rotate. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record the matching prefix and conversion boundary. If this check fails, mark the claim unavailable and repair the method before continuing.

Name the relevant declaration, source values, weights, positions, progress, easing, color space, transform list, property animation type and browser state.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

6. Extend shorter lists with identity functions

When corresponding transform lists differ in length, the shorter list can be extended with identity functions matching the longer list before interpolation.

Original worked example. scale(2) versus none uses scale(1) at the neutral end. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Add rotate to the longer list. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record generated identity functions. If this check fails, mark the claim unavailable and repair the method before continuing.

Archive source, fixture, rules, computed styles, browser version and raw exceptions so another reader can reproduce the conclusion.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

7. Recognize matrix fallback

Nonmatching remainder functions may be converted to matrices and interpolated under the transform specification. A matrix result can hide the author’s original function structure.

Original worked example. rotate versus translate reaches matrix interpolation. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Make both functions translate. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Compare function interpolation with matrix fallback. If this check fails, mark the claim unavailable and repair the method before continuing.

Keep grammar, payload type, normalization, active interval, interpolation rule and computed result in separate fields so equal output cannot rewrite the mechanism.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

8. Trace mapping progress

transform-interpolate() selects an interval from the fixed stop map and converts global progress into local progress for that interval.

Original worked example. 70% in a 60%-to-100% interval is one quarter through that segment. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Move the middle stop to 80%. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Save global and local progress. If this check fails, mark the claim unavailable and repair the method before continuing.

Use a positive case, a clean negative case and an unavailable case. Unavailable means the required syntax or evidence was not established.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

9. Apply easing to progress, not weights

Mapping easing changes the progress path through an interval. It does not rebalance transform-mix contributions.

Original worked example. ease-in delays movement near the interval start. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Switch to linear. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record raw progress, eased progress and matrix. If this check fails, mark the claim unavailable and repair the method before continuing.

Change one consequential premise while keeping the rest fixed. Predict the new branch before inspecting it and preserve disagreement.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

10. Use a three-stop path

Multiple stops can define a path that first translates and then rotates. A weighted mix combines all named contributions rather than traversing that path segment by segment.

Original worked example. At 40%, only the first segment is active. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Change progress to 80%. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Identify the active stop pair. If this check fails, mark the claim unavailable and repair the method before continuing.

Carry one plausible alternative through the ledger, then choose the next observation that separates it from the leading account.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

11. Keep transform origin separate

Transform origin changes the rendered geometry around the same transform matrix. Neither mix nor mapping syntax replaces origin evidence.

Original worked example. Two equal matrices move boxes differently with different origins. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Hold the origin constant. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Archive transform-origin and box dimensions. If this check fails, mark the claim unavailable and repair the method before continuing.

Name the relevant declaration, source values, weights, positions, progress, easing, color space, transform list, property animation type and browser state.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

12. Handle singular matrices

A scale crossing zero can create a non-invertible transformation matrix and temporarily prevent rendering. That observation is about the transform result, not proof of either control function.

Original worked example. scale from 1 to -1 crosses zero. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Change the endpoint to .5. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record determinant and visibility state. If this check fails, mark the claim unavailable and repair the method before continuing.

Archive source, fixture, rules, computed styles, browser version and raw exceptions so another reader can reproduce the conclusion.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

13. Test equal matrices with different histories

Different lists and control models can resolve to the same matrix at one sampled progress. A single matrix snapshot cannot reveal the route.

Original worked example. A translation literal and a mapped transform both serialize to the same matrix. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Sample at a second progress. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Preserve source functions and control inputs. If this check fails, mark the claim unavailable and repair the method before continuing.

Keep grammar, payload type, normalization, active interval, interpolation rule and computed result in separate fields so equal output cannot rewrite the mechanism.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

14. Separate document time from explicit progress

A progress source may come from a percentage or other supported source; an animation timeline is only one possible context. Do not invent elapsed time where the declaration supplies a fixed coordinate.

Original worked example. 75% is fixed in the fixture. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Drive progress from a timeline where supported. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record source provenance and sampling time. If this check fails, mark the claim unavailable and repair the method before continuing.

Use a positive case, a clean negative case and an unavailable case. Unavailable means the required syntax or evidence was not established.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

15. Treat unsupported syntax as unavailable

A browser that rejects the proposed function has not chosen identity or the first stop. A tested baseline transform must remain earlier in the cascade.

Original worked example. transform:translateX(30px) survives a rejected draft declaration. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Use a supporting build. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record parser support, winning declaration and computed matrix. If this check fails, mark the claim unavailable and repair the method before continuing.

Change one consequential premise while keeping the rest fixed. Predict the new branch before inspecting it and preserve disagreement.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

16. Do not infer mechanism from motion

The same motion can come from transitions, keyframes, scroll timelines, JavaScript or either proposed function. Video evidence alone is underdetermined.

Original worked example. A box follows the same sampled positions. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Inspect declarations and timeline state. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Require source-led evidence. If this check fails, mark the claim unavailable and repair the method before continuing.

Carry one plausible alternative through the ledger, then choose the next observation that separates it from the leading account.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

17. Build a reproducible transform matrix

Cover identity remainder, excess weights, reordered functions, differing list lengths, matrix fallback, multiple stops, easing, singular matrices and unsupported syntax.

Original worked example. The table pairs source lists with matrices and visible geometry. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Repeat with transform origins and 3D functions. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Version markup, draft and browser. If this check fails, mark the claim unavailable and repair the method before continuing.

Name the relevant declaration, source values, weights, positions, progress, easing, color space, transform list, property animation type and browser state.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents · Next chapter

18. Use the owning specifications and continue

Values Level 5 owns the proposed control functions; Transforms Level 1 owns list and matrix interpolation; Web Animations provides the wider animation model.

Original worked example. The route follows grammar, identity, list interpolation, mapping and rendering. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. When the draft changes, rerun every matrix fixture. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Save exact source URLs, access date and raw matrices. If this check fails, mark the claim unavailable and repair the method before continuing.

Archive source, fixture, rules, computed styles, browser version and raw exceptions so another reader can reproduce the conclusion.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, payload type, weights or positions, progress, interpolation rule and first missing obligation; change one condition and mark the first unsupported inference. Preserve the raw trace beside the revised result. End the chapter with three sentences: what the evidence establishes, what it does not establish and what observation would change the conclusion. This keeps the lesson useful when the browser, stylesheet or document state changes. A strong record also names the datum, denominator, section or coordinate system that governed the decision, so a later reader can repeat the reasoning without importing an unstated shortcut.

Previous chapter · Contents

Sources and further study

CSS Values and Units Module Level 5. Used for the standard definitions, material mechanisms or method limits developed in this lesson.

CSS Transforms Module Level 1. Used for the standard definitions, material mechanisms or method limits developed in this lesson.

Web Animations. Used for the standard definitions, material mechanisms or method limits developed in this lesson.

The worked examples and transfer checks are developed here and state their own assumptions. The linked sources support the underlying CSS grammar, normalization, interpolation and cascade principles.

Return to contents · Return to The Gold Standard of Websites