Aglet

Triage preview orientation that differs from the final file

An image can store pixels in one orientation and describe its intended display orientation separately. Triage should capture the source metadata, local preview, processing result, and final file for one fixture. The key is to distinguish a rendering difference from a transform that changes delivered pixels.

Establish what is happening

  1. Capture the orientation fixture

    Record image dimensions, pixel arrangement, orientation metadata, preview dimensions, and the final file reference. Use a fixture with an obvious corner or label so a quarter-turn or mirror change is visible rather than judged from a symmetric scene.

  2. Compare each boundary

    Inspect raw pixels and metadata before preview, after any processing step, and in the delivered output. Note whether the preview applies metadata at display time, whether processing normalizes pixels, and whether metadata is preserved or removed.

  3. Classify the drift

    Classify the case as preview-only rendering, metadata loss, double rotation, processing transform, or unclear output. Record the expected orientation rule and the user-visible consequence for downstream viewing or editing.

What to carry forward

Triage is complete when the fixture, metadata, preview, and final output are compared at named boundaries. If the final consumer's orientation rule is unknown, record that dependency instead of declaring the preview or file objectively wrong.

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