Check whether the outcome improved
Run lifecycle sequences
Add several files, replace one, remove from the middle, reorder items, trigger a preview error, and leave and return. Repeat with different dimensions and record visible items plus settled resource or memory observations after each sequence.
Check release boundaries
Confirm resources associated with removed previews are released or intentionally shared, and that hidden detached elements do not retain file data. Verify a full page exit is not the only event that clears resources unless that limitation is documented.
Exercise later use
After repeated changes, select another large file and complete the workflow. Check preview quality, controls, validation, and form state, ensuring cleanup did not release data still needed by a visible item or leave stale references.
What to carry forward
Accept preview lifecycle behavior when repeated actions remain usable, removed resources have a documented release or reuse policy, and memory evidence does not show unexplained sustained growth. Fail the shortest sequence that leaves hidden resources or prevents a later preview.
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