Aglet

Investigate image orientation drift from preview to output

Investigation should follow both pixels and metadata because either can carry the display instruction. Use a fixture with known landmarks and compare raw and rendered states at every boundary. The brief should identify the first transform or metadata loss that explains the final view.

Build a useful investigation brief

  1. Build orientation contrasts

    Prepare images whose pixels are deliberately stored sideways, upright with metadata, and upright without metadata. Record the expected visible orientation and dimensions for each so a renderer or processor cannot hide the distinction.

  2. Trace pixel and metadata state

    At selection, preview, processing, storage, and download, record pixel dimensions, orientation metadata, transforms, and rendered result. Mark where metadata is normalized, discarded, or applied, and keep the source fixture paired with each output.

  3. Test consumer differences

    Render the final file through the actual review path and a neutral image reader when available. Compare results and explain whether a mismatch comes from a consumer contract, an earlier transform, or a missing output property.

What to carry forward

The investigation is sufficient when a landmarked fixture shows where the visible orientation diverges and whether pixels or metadata changed first. If downstream behavior cannot be observed, report the stored output state and the unresolved consumer assumption.

Technical background: MDN reference.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow