Explainer ·
The Snapshot Waiting Behind the Back Button
Two things used to guarantee the back button reloads a page from scratch. Chrome rewired one in 2025 and is deleting the other in 2026, mid-rollout right now.
10 articles, newest first.
Explainer ·
Two things used to guarantee the back button reloads a page from scratch. Chrome rewired one in 2025 and is deleting the other in 2026, mid-rollout right now.
Explainer ·
Your light or dark mode setting can leave the machine as an HTTP request header. The same channel carries your motion and contrast preferences too.
Explainer ·
The User-Agent string was trimmed to leak less. The detail it carried did not disappear - it moved to a channel the server switches on, and one engine answers.
Explainer ·
Before your JavaScript runs, the browser can already have told the server how much RAM your device has and how fast your connection is, rounded off on purpose.
Explainer ·
Two hundred milliseconds of hover can be enough for the destination to load in full, run all of its JavaScript, and count you as a visitor.
Explainer ·
A kilobyte is treated as a fixed unit of harm. It is not: a kilobyte of JavaScript and a kilobyte of image do very different amounts of damage.
Explainer ·
The same page can hand two people different encodes of one video. A negotiation before playback picks which, and the browser's answers are deliberately vague.
Explainer ·
Loading a page is not a neutral act. A set of identifying details arrives with the request itself, before any script runs and before you touch the screen.
Explainer ·
A script tag and an iframe look like the same act of embedding. They are opposites: one hands over the page, the other holds the guest at arm's length.
Explainer ·
A video is not a file you are sent. It is a few hundred short segments, published at several qualities, and a running guess about which one to fetch next.