Skip to Content
Platform.Ontology

Push history entries (back button limits)

Adds fake history entries so Back does less than expected; browsers skip entries made without a click.

Does something on your deviceThings a page can doWindows and navigationWeb browsersWhile you use it

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

Chromeworks
Edgeworks
Firefoxworks
Safariworks
iPhoneworks
Androidworks
Samsungworks
BrowserStatusFirst versionReleasedNote
ChromeSupported52010-05-25None
EdgeSupported122015-07-29None
FirefoxSupported42011-03-22None
SafariSupported52010-06-07None
Safari on iPhoneSupported42010-06-21All iOS browsers use WebKit
Chrome on AndroidSupported182012-06-27None
Samsung InternetSupported1.02013-04-27None

How a site asks for it

APIhistory.pushState(), replaceState(), scrollRestoration; Navigation API
Browser compat keysapi.History.pushState
api.History.replaceState
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
Activationnone
How long it lastsEntries live in the tab session history
How to take it backNothing to revoke (no permission is stored)
Inside an iframeSame-origin URLs only; cross-origin frames affect the joint session history of the tab

Typical flow

  1. Call pushState with a same-origin URL
  2. Entry appears in session history
  3. 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

TypeExampleApps
socialScrolling a feed and tapping a post gives a new address, so Back returns you to the feed.Instagram web, X
shoppingA product filter updates the URL so you can share the filtered list.Amazon
productivityOpening a document in a web app gives it its own link without a full page load.Google Docs, Notion
adsSome ad pages stuff the Back list so that pressing Back leads to another ad page.None named
mediaA streaming site opens a title in a panel and still lets Back close it.Netflix
analyticsAnalytics 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

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility5 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough 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)

Sources

How well checked: Based on official documentation.

On this page