Scroll Position from Progress

Invert normalized scroll progress into a position using explicit content/viewport extents.

Description

Invert normalized scroll progress into a position using explicit content/viewport extents.

Scroll progress scales over the content extent that lies beyond the viewport, not over the full content size.

When to use this tool

Invert normalized scroll progress into a position using explicit content/viewport extents.

  • Prepare the supplied progress, contentExtent, viewportExtent fields for this operation.
  • Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

  1. Enter progress, contentExtent, viewportExtent. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.scrollPosition. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require progress between zero and one and nonnegative extents. Return progress*max(0,contentExtent-viewportExtent).1

Input fieldMeaning and representationAccepted input
progressprogress.Finite number; from zero through one inclusive
contentExtentcontent extent.Finite number; zero or greater
viewportExtentviewport extent.Finite number; zero or greater
Output fieldInterpretation
resultObject containing the named outputs below.
result.scrollPositionThe scroll position value under the stated formula or text convention.
json
{
  "input": {
    "progress": 0.25,
    "contentExtent": 200,
    "viewportExtent": 100
  },
  "output": {
    "result": {
      "scrollPosition": 25
    }
  }
}

Limitations and assumptions

  • This is a coordinate conversion, without scrolling or browser-specific origin behavior. Nonoverflowing content returns zero position.
  • Rectangle arrays use [x,y,width,height] with nonnegative extents. All dimensions must use the same coordinate frame and unit; values are supplied rather than measured from a page.
  • Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
  • String lists have at most 128 entries of at most 128 code units; matrices have at most 128 rows and columns. Larger numeric lists and parsed JSON have separate bounded budgets. Nonfinite results and excessively large serialized outputs are rejected.
  • Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Alternative or Complementary methods

Measure the actual layout when browser behavior matters. The formulas use supplied coordinates and explicit simplifications; they do not account for every box, writing mode, clipping ancestor or simultaneous layout change.

References

  1. Tool behavior and example: Scroll Position from Progress — tool.io

Similar or alternative tools

  • Scroll Position after Item Resize

    Adjust scroll position only when a resized item is independently established before the anchor; retain signed extent change and do not infer overlapping-anchor behavior.

  • Scroll Position after Prepend

    Preserve an existing scroll anchor after a known prepended extent, before any independently required scroll-range clamp.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies