Check whether the outcome improved
Run size boundaries
Test below-limit, exact-limit, above-limit, and context-specific limit fixtures. Record raw bytes, displayed size, early guidance, transfer start, and final outcome. Include a size that exposes any unit or rounding ambiguity.
Inspect each user surface
Review picker text, form copy, progress state, response, validation message, and processing status. Verify the same contextual limit and units appear where a decision is possible, without suggesting that transfer itself proves eligibility.
Follow rejection recovery
Attempt the documented reduction, replacement, or retry path and confirm it works for a compliant file. Ensure an oversized file does not remain marked ready, and that an error after transfer explains why repeating the same upload will not help.
What to carry forward
Accept the limit behavior when boundary files receive consistent decisions, units are understandable before transfer, and rejection offers a valid next action. Fail any case where the limit shifts without context or users learn in the final stage that the transfer was never eligible.
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