title: Chrome popstate not firing on Back Button if no user interaction
body: <p>I'm trying to use "pushState" and the "popstate" event to trap Back button navigation, however, while the popstate event triggers correctly in Firefox, it doesn't trigger in Chrome (Version 76.0.3809.87 (Official Build) (64-bit)) <strong>if there is no user interaction</strong>.</p>
  
  <p>From testing, it looks like the popstate event only gets triggered if the user interacts with the page (ie. clicks somewhere on the document). So if you load the page without interacting and hit Back, the popstate function is not called.</p>
  
  <p>I've added a Fiddle to showcase this: <a href="https://jsfiddle.net/0xwvLndu/" rel="noreferrer">https://jsfiddle.net/0xwvLndu/</a></p>
  
  <p>To test the Fiddle in Chrome, just click the link and hit the Back button. You'll see no alert. Then click the link again but this time click anywhere on the Fiddle document and then hit the Back button, the alert is then triggered.</p>
  
  <p>I found a discussion on the Chromium forum that may relate to this quirk, and perhaps this has been implemented to prevent abuse of history entries - <a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/OCS7g72HtyI" rel="noreferrer">https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/OCS7g72HtyI</a> and <a href="https://github.com/WICG/interventions/issues/21#issuecomment-425609246" rel="noreferrer">https://github.com/WICG/interventions/issues/21#issuecomment-425609246</a></p>
  
  <p>If this is the case, does it mean that popstate cannot be relied on anymore to trap Back button actions, and if so, is there a work around solution?</p>
  
  <p>Below is an example of what I've been testing with:</p>
  
  <pre><code>window.addEventListener('load', function() {
      history.pushState(null, null, document.URL);
  });
  
  window.addEventListener('popstate', function(event) {
      alert('test');
  });
  </code></pre>
  
  <p>I expected the alert to be triggered on Back Button regardless of user interaction, but this does not happen in Chrome.</p>