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 progress() Normalization from calc() Arithmetic

With progress(75px, 50px, 150px), the normalized result is 0.25. At 200px the default result clamps to 1, while progress(no-clamp 200px, 50px, 150px) can yield 1.5. A hand-written calc((200px – 50px) / (150px – 50px)) also yields 1.5; adding min() and max() would be a separate author decision.

This lesson continues The Gold Standard of Websites, the Gold Standard of Education and the How X Works hub. Every value, endpoint, normalized result and computed property is an original synthetic fixture. The lesson does not promise shipping support, equate numeric progress with animation-timeline progress or hide the draft’s open questions and edge cases.

Record input calculations, resolved types and units, start, end, no-clamp flag, raw quotient, clamped result, equal-endpoint branch, destination property grammar, browser build and unavailable behavior.

The CSS Values and Units Module Level 5 defines progress() and states that it is syntactic sugar for a particular calc() pattern, with explicit default clamping and equal-endpoint behavior. The CSS Values and Units Module Level 4 defines calc() and other math functions. Values Level 5 remains an early-exploration editor’s draft and even records open questions about progress() clamping, so all claims are dated.

THE GOLD STANDARD · WEBSITES

progress() expresses normalized position between endpoints; calc() supplies general arithmetic

The proposed progress(value, start, end) notation computes (value – start) / (end – start) when the endpoints differ and returns a number. It clamps the result to zero through one unless no-clamp is specified. calc() can express the same algebra when units permit, but it does not automatically clamp, define the equal-endpoint branch or communicate the normalized-progress job.

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 normalization and arithmetic different jobs

progress() encodes a proportional-distance contract with endpoints and default clamping. calc() evaluates the arithmetic expression the author writes.

Original worked example. 75px between 50px and 150px normalizes to .25. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Write the quotient manually in calc(). State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record raw quotient and final clamped result. If this check fails, mark the claim unavailable and repair the method before continuing.

Keep grammar, substitution, evaluation, cascade and computed result in separate fields so matching pixels cannot rewrite the mechanism.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, token stream, condition, calculation or destination grammar and the 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. Use the correct argument order

The first argument is the progress value, followed by start and end. Reordering endpoints changes direction and can change clamping.

Original worked example. progress(75px,50px,150px) gives .25. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Swap start and end. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Store all three resolved values before simplifying. 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, token stream, condition, calculation or destination grammar and the 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. Require consistent types

The three calculations must resolve to a consistent number, dimension or percentage type. A length cannot be normalized directly against angles.

Original worked example. px and rem resolve to lengths in context. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Replace the end with 180deg. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Inspect type resolution and invalidation. 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, token stream, condition, calculation or destination grammar and the 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. Make default clamping explicit

Without no-clamp, results below zero become zero and results above one become one. calc() does not add this bound.

Original worked example. 200px against 50px to 150px clamps to one. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Add no-clamp. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Save raw and returned values. 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, token stream, condition, calculation or destination grammar and the 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. Use no-clamp deliberately

no-clamp permits extrapolated numbers outside zero to one. It is not a request to ignore type consistency or invalid calculations.

Original worked example. 25px maps to -.25 when unclamped. 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 an angle. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record flag and validity separately. If this check fails, mark the claim unavailable and repair the method before continuing.

Name the relevant declaration, token stream, candidate, condition, random key, calculation or destination property.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, token stream, condition, calculation or destination grammar and the 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. Handle equal endpoints

When start equals end, the draft defines special results rather than dividing blindly by zero. The default clamped branch returns zero.

Original worked example. progress(10px,5px,5px) returns zero by default. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Use no-clamp with input below, equal to and above the shared endpoint. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Capture zero, negative infinity or positive infinity behavior under the draft. 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, token stream, condition, calculation or destination grammar and the 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. Separate progress from percentage

progress() returns a number, not automatically a percentage. The destination expression decides how that number is used.

Original worked example. Opacity consumes .25 directly while a translation multiplies it by 100%. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Insert the number where a length is required without multiplication. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Inspect destination typing. If this check fails, mark the claim unavailable and repair the method before continuing.

Keep grammar, substitution, evaluation, cascade and computed result in separate fields so matching pixels cannot rewrite the mechanism.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, token stream, condition, calculation or destination grammar and the 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. Keep contextual percentages visible

Percentage arguments must resolve consistently in the property context. An unresolved or incompatible percentage can make the function invalid.

Original worked example. Three percentages share the same reference basis. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Mix a length with an unresolved percentage. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record percentage basis and resolved type. 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, token stream, condition, calculation or destination grammar and the 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. Compare readable intent

A manual calc quotient can be mathematically equivalent, but progress() names the normalization job and supplies the draft’s edge behavior. Equivalence must include clamping and equal endpoints.

Original worked example. Both forms yield .4 inside the interval. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Move the input beyond the end. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Compare results over below, within and above ranges. 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, token stream, condition, calculation or destination grammar and the 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. Do not confuse timeline progress

A normalized number from progress() is not itself a scroll timeline, animation attachment range or animation effect progress. It may be used in values independently of animation.

Original worked example. A width-dependent color mix uses progress() with no animation. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Attach an animation to a scroll timeline. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Keep value computation and timeline state in separate ledgers. 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, token stream, condition, calculation or destination grammar and the 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. Use monotonic controls

With start less than end and no other changes, increasing the input should not decrease the unclamped result. Reversed endpoints reverse that relationship.

Original worked example. Inputs 50, 75 and 150px yield 0, .25 and 1. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

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

Practical evidence check. Plot the three calculated points and boundaries. If this check fails, mark the claim unavailable and repair the method before continuing.

Name the relevant declaration, token stream, candidate, condition, random key, calculation or destination property.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, token stream, condition, calculation or destination grammar and the 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. Test destination range separately

A valid progress number can still be constrained or interpreted by the receiving property or function. Destination behavior is not part of normalization.

Original worked example. A number feeds a color mix weight after conversion. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Feed it into an integer-only context. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Record normalization success and destination acceptance. 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, token stream, condition, calculation or destination grammar and the 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. Preserve custom-property substitution

Arguments can contain var() and other calculations. Resolve them before judging consistent types or the final quotient.

Original worked example. Start and end come from registered length custom properties. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Change one property to an unregistered color token. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Archive substituted calculations. If this check fails, mark the claim unavailable and repair the method before continuing.

Keep grammar, substitution, evaluation, cascade and computed result in separate fields so matching pixels cannot rewrite the mechanism.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, token stream, condition, calculation or destination grammar and the 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. Treat open draft questions honestly

The draft records open questions about progress clamping. Current text supports a dated explanation, not a permanent platform guarantee.

Original worked example. The fixture cites the 6 November 2026 editor’s draft behavior. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Re-run after a later draft revision. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Save source date and changed section. 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, token stream, condition, calculation or destination grammar and the 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 progress() has not computed zero. A baseline value or equivalent tested calc pattern is required.

Original worked example. Opacity .5 remains when a later progress() declaration is dropped. 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 and computed value. 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, token stream, condition, calculation or destination grammar and the 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. Repair the screenshot shortcut

The same final property value can come from clamping, an in-range quotient, a baseline declaration or a manual calc. Pixels alone do not identify the path.

Original worked example. Four fixtures all show opacity one. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Inspect matched rules and calculated inputs. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Require computation 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, token stream, condition, calculation or destination grammar and the 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 normalization ledger

Preserve resolved inputs, types, quotient, clamping, equal-endpoint branch, final number and destination result.

Original worked example. The matrix covers below, inside, above, reversed, equal and incompatible endpoints. The declarations, values and observations are explicit so the reader can reconstruct the decision instead of trusting a label.

Changed-context transfer. Repeat with percentages and custom properties. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

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

Name the relevant declaration, token stream, candidate, condition, random key, calculation or destination property.

Before closing, reconcile the original fixture against the chapter rule: identify the declaration, token stream, condition, calculation or destination grammar and the 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 Values Levels 5 and 4 and continue

Level 5 owns progress(); Level 4 owns calc(); the scroll-timeline article owns animation-range progress rather than this value function.

Original worked example. The route follows types, quotient, edges, clamping and destination use. 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 boundary case. State what changed, predict the consequence and revise only the conclusion that depended on that condition.

Practical evidence check. Save source URLs, access date and raw computed styles. 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, token stream, condition, calculation or destination grammar and the 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 Values and Units Module Level 4. Used for the standard definitions, material mechanisms or method limits developed in this lesson.

CSS Scroll-driven Animations Module Level 1. 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 parsing, substitution, evaluation and cascade principles.

Return to contents · Return to The Gold Standard of Websites