Aglet

Verify a fix for a browser-specific regression

Verification should prove the original browser failure is addressed without changing behavior elsewhere. Replay the same task and state, then check ordinary and recovery paths where the browser difference could return.

Check whether the outcome improved

  1. Replay the failing matrix row

    Use the original browser version, operating system, viewport, zoom, input mode, account state, revision, and fixture where available. Record any missing condition that lowers confidence.

  2. Compare a working row

    Run the same task in a known-good browser or version and compare data, requests, rendered state, focus, layout, and completion. Confirm the fix did not merely hide the visible symptom.

  3. Check adjacent states

    Review refresh, back navigation, validation, loading, empty, and narrow states relevant to the failure. Apply the browser checkpoint and keep the result partial if an affected version remains untested.

What to carry forward

Verification should state fixed in the failing context, regressions found, partial coverage, or inconclusive. Close only when the original browser row completes the task and the matched comparison remains healthy. Replay the same fixture and interaction sequence in the affected and working browsers, then test a fresh session and a realistic narrow viewport before closing.

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