An hour of form-filling, gone on one accidental refresh
You fill a giant browser form — say the 8-page IRS W-8BEN-E. One ⌘R, back-swipe, or tab close, and it's all erased. No warning. No draft. Start over.
Facts cited
| Internet users worldwide | ~5.5 billion | ITU / analyst estimates, 2026 |
|---|---|---|
| Global life expectancy | 73 years | World Bank, 2023 |
| IRS's own burden estimate (sibling form W-8BEN) | 7 hr 24 min | Paperwork Reduction Act notice |
| Withholding if the form is botched/unfiled | 30% of gross | IRS foreign-payee rules |
Assumptions low → high
| What we can't measure | low | likely | high |
|---|---|---|---|
| Internet users filling a long browser form on a given day | 0.5% | 1% | 1.5% |
| Of those, the share who suffer a loss event mid-fillRefresh, back button, tab close, crash, or session timeout. | 0.5% | 1% | 1.5% |
| Minutes to re-enter what was lostConservative — a lost W-8BEN-E alone is the IRS's estimated hours, not minutes. | 5 min | 10 min | 15 min |
Who can fix it
- Owner
- Form owners (web) · Chromium PDF team · IRS Office of Online Services
- Channel
- Form libraries (default autosave) · issues.chromium.org (Internals > Plugins > PDF) · IRS digital-services feedback
The poster child is the IRS W-8BEN-E — 8 pages, ~30 parts, filled by every non-US entity that ever invoices a US company. But it’s every long browser form: job applications, visa paperwork, insurance claims, government portals. You pour in an hour. One accidental refresh, and the browser pretends you never existed.
This one was reproduced by hand: typed a name into the fillable PDF, closed it — everything erased. Bizarrely, insanely normal.
The math
5.5B users × 1% × 1% = 550K loss events / day
550,000 × 10 minutes = 330 million seconds / day ≈ 3,800 human years / year ≈ ~52 lifetimes / year. The band runs from 7 (low) to ~175 (high) lifetimes.
Second-order waste — directional, only pushes up
- Real money, not just time. A botched or unfiled W-8BEN-E means the withholding agent keeps 30% of gross US-source payments. This paper-cut costs foreign freelancers and small firms actual income.
- The defensive-typing tax. Burned users now draft every form’s answers in a separate doc and paste them in — a permanent overhead paid forever, caused by the memory of one loss.
- Support load. “I lost my form” tickets, resent links, expired-session escalations.
The fix has three layers
The floor is a dirty-state beforeunload guard — a handful of lines that pops “you have
unsaved changes.” The real fix is draft persistence (autosave to localStorage or server),
which makes the loss impossible rather than merely warned-about.
| Layer | Fix | Owner |
|---|---|---|
| Web forms | Dirty-state guard + autosave. Register beforeunload only while dirty (it disables the back/forward cache otherwise) |
Form libraries — fix the default, not one site |
| Browser PDF | Chrome already restores HTML form state on back/refresh. The PDF viewer should do the same, and warn on dirty unload | Chromium PDF team |
| The form itself | A fillable PDF is the wrong medium for a 30-part form. Web-native with saved state — the IRS already proved it can with Direct File | IRS Office of Online Services |
The pattern is already solved: the GOV.UK Design System mandates “save and come back later” for long government forms. It’s just not deployed everywhere.
Repro status
✅ Confirmed by hand — typed into the fillable PDF, closed it, data gone. No warning.
Cross-browser comparison not yet done. The “no warning on refresh” claim is confirmed only for the case above. Chrome’s PDF-viewer behaviour has shifted across versions, so before this is cited anywhere it needs verifying against current Chrome, Firefox, Safari and Edge — screen-recorded, as a comparison table, for the Chromium issue.
Until that’s done, treat the browser-layer claim as one reproduction, not a survey. The time math above doesn’t depend on it: it rests on long web forms generally, not on any one browser’s PDF handling.
Difficulty to fix: easy
You typed for an hour. The browser watched every keystroke. One refresh and it acts like you were never there. A five-line dirty-state guard — or a browser that treats PDF forms the way it already treats HTML forms — saves ~50 lifetimes a year. GOV.UK solved this pattern years ago.