Push history entries (back button limits)
Adds fake history entries so Back does less than expected; browsers skip entries made without a click.
In one line
Can add extra Back button steps, but browsers skip steps made without a tap
Adds fake history entries so Back does less than expected; browsers skip entries made without a click.
A site can change the address bar and history without loading a page. Misused, it traps the back button and keeps the person on the site, so browsers now skip entries added with no user interaction.
What it can and can't do
What the user does: Nothing. It happens as you move around the page, or after your first tap.
It can
- Change the address bar to a new page address without a full reload
- Add steps so Back goes to a screen inside the app
- Keep the Back button working in apps that load pages without reloading
It cannot
- Trap you for good on a page, because browsers skip steps made without a click or tap
- Change the address to a different website
- Hide where you actually are from the browser
- Block you from leaving through the address bar or a bookmark
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 5 | 2010-05-25 | None |
| Edge | Supported | 12 | 2015-07-29 | None |
| Firefox | Supported | 4 | 2011-03-22 | None |
| Safari | Supported | 5 | 2010-06-07 | None |
| Safari on iPhone | Supported | 4 | 2010-06-21 | All iOS browsers use WebKit |
| Chrome on Android | Supported | 18 | 2012-06-27 | None |
| Samsung Internet | Supported | 1.0 | 2013-04-27 | None |
How a site asks for it
| API | history.pushState(), replaceState(), scrollRestoration; Navigation API |
| Browser compat keys | api.History.pushStateapi.History.replaceState |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| Activation | none |
| How long it lasts | Entries live in the tab session history |
| How to take it back | Nothing to revoke (no permission is stored) |
| Inside an iframe | Same-origin URLs only; cross-origin frames affect the joint session history of the tab |
Typical flow
- Call pushState with a same-origin URL
- Entry appears in session history
- Back button or Navigation API fires popstate
Data you get
Shape: none
No individual data fields. The signal is the access itself.
Technical limits
- URL must be same origin as the document (SecurityError otherwise); no cross-origin path spoofing
- Chrome 75 history manipulation intervention: entries added by pages that had no user interaction are skipped by Back and the long-press history menu
- State object serialized size limit about 16 MiB in Firefox (browser.history.maxStateObjectSize 16 MiB); Chrome has no fixed limit but is IPC bound
- Rate limits: Safari throws SecurityError after about 100 calls in 30 s; Firefox after about 200 calls in 10 s; Chrome throttles flood of navigations
- Page cannot read other sites' history entries or the length beyond history.length (capped at 50 in Chrome, 50 to 1000 depending on browser)
The story
What it is
A site can add steps to your Back button list, and sometimes abuse it.
For you
When you move around a single page app, the address changes and Back works as you would expect. On bad sites, Back may seem broken because the page piled up extra entries.
For makers
Single page apps use it to give each view its own link without reloading. Shady sites use it to trap people, so browsers now skip entries made without a click.
Where you see it
| Type | Example | Apps |
|---|---|---|
| social | Scrolling a feed and tapping a post gives a new address, so Back returns you to the feed. | Instagram web, X |
| shopping | A product filter updates the URL so you can share the filtered list. | Amazon |
| productivity | Opening a document in a web app gives it its own link without a full page load. | Google Docs, Notion |
| ads | Some ad pages stuff the Back list so that pressing Back leads to another ad page. | None named |
| media | A streaming site opens a title in a panel and still lets Back close it. | Netflix |
| analytics | Analytics tools watch history changes to count a new page view in single page apps. | Google Analytics |
Risks
- Back button traps
- Messy page counts
What the platform says
- Mozilla: History API. MDN says pushState lets a page change the address bar and history without reloading.
Good uses and abuse
Legitimate uses
- Single page app routing
- Filter state in URL
- Modal state
Known abuse
- Back button trap
- Forced exit prompt chains
- Fake deep links
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 5 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2019-06, Chrome 75: History manipulation intervention: skip entries without user activation
- 2022-02, Chrome 102: Navigation API ships with entries() same-origin only
- 2025, Chrome 138: Chrome documents back-button hijacking as a spam behavior in Search and tightens intervention coverage (verify current status)
Related capabilities
Related
- Navigation API. Can watch and control page changes inside the app, such as when you press Back
- Leave-page confirmation (beforeunload). Can show a generic Leave site? warning when you close or leave, after you have interacted
Sources
How well checked: Based on official documentation.