Build a useful investigation brief
Create a browser matrix
List engine, version, operating system, viewport, zoom, input mode, account state, and outcome for each run. Hold the application revision and fixture constant wherever possible.
Trace the first divergence
Compare request, response, DOM or semantic state, focus, layout, storage, and timing at the failing action. Record safe errors and identify whether the browser receives different data or renders it differently.
Test nearby conditions
Vary one browser condition at a time, such as version, viewport, cached state, input, or feature support. Keep each result tied to the original task and record counterexamples to the leading explanation.
What to carry forward
The brief should show the matched browser matrix, first divergent boundary, representative evidence, and competing explanations. Conclude engine-specific, data or state-related, general product defect, or unresolved with confidence. Compare identical markup, requests, console-visible symptoms, layout measurements, storage state, and interaction timing across browsers to isolate the first divergence. Check whether the divergence survives a fresh profile and a reduced fixture before attributing it to the browser engine.
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