Build a useful investigation brief
Compare responsive structure
Inspect the rendered heading, navigation, setup action, form controls, and result links at the narrow viewport. Record actual dimensions and overflow symptoms from the browser. Compare desktop and narrow DOM order where useful, without replacing server-rendered content with a separate mobile workflow.
Trace input and keyboard
Enter valid and invalid synthetic values, open and close the keyboard, scroll to errors, and submit. Record focus, viewport resize, preserved input, and validation response. Distinguish a control hidden by layout from a server rejection with identical visible wording.
Follow setup persistence
Create or resume a workspace, project, test key, and built-in check on narrow layout, then refresh and return through links. Compare durable state and route context with desktop. Note browser behavior the harness cannot control, such as OS keyboard timing, as an explicit unknown.
What to carry forward
The investigation is ready when the narrow-screen divergence is tied to a rendered element or state transition and compared with the same desktop journey. Deliver viewport, focus, response, redirect, and durable-state evidence with browser limits recorded.
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