The popstate only contains a state when there is one. When it goes like this: initial page loaded new page loaded, with state added via pushState back button pressed then there is no state, because the initial page was loaded regularly, not with pushState. As a result, the onpopstate event is fired with a state … Read more
By default, the browser’s back button does not send a HTTP request to the server at all. Instead, it retrieves the page from the browser cache. This is essentially harmless, but indeed confusing to the enduser, because s/he incorrectly thinks that it’s really coming from the server. All you need to do is to instruct … Read more
The ‘popstate’ event only works when you push something before. So you have to do something like this: jQuery(document).ready(function($) { if (window.history && window.history.pushState) { window.history.pushState(‘forward’, null, ‘./#forward’); $(window).on(‘popstate’, function() { alert(‘Back button was pressed.’); }); } }); For browser backward compatibility I recommend: history.js
This is because of the back-forward cache in Safari. You can use the following code to force a reload when the back-button is pressed. window.onpageshow = function(e) { // e -> event if (e.persisted) { window.location.reload(); } }; Additionally, if you are using jQuery … $(window).bind(“pageshow”, function(e) { // e -> event if (e.originalEvent.persisted) { … Read more
Make sure your AJAX requests use a different URL from the full HTML documents. Chrome caches the most recent request even if it is just a partial. https://code.google.com/p/chromium/issues/detail?id=108425
How about using setCancelable? Did you try it? From the Docs: Control whether the shown Dialog is cancelable. Use this instead of directly calling Dialog.setCancelable(boolean), because DialogFragment needs to change its behavior based on this For custom DialogFragment Add isCancelable = false at onCreateDialog
The easier way is to wrap the body in WillPopScope, in this way it will work with the Back Button on the Top AND the Android Back Button on the Bottom. Here an example where both back buttons return false: final return = Navigator.of(context).push(MaterialPageRoute<bool>( builder: (BuildContext context) { return Scaffold( appBar: AppBar( title: Text(“New Page”), … Read more
If I assume you’re using android.support.v4.widget.DrawerLayout in your layout, then this approach may work for you; I’ve only tested on API 21 but given it’s mostly using the support libraries, it should work (famous last words) on lower or higher targets. import android.support.v7.app.ActionBarDrawerToggle import android.support.v4.widget.DrawerLayout ActionBarDrawerToggle mDrawerToggle; DrawerLayout drawerLayout; private boolean mToolBarNavigationListenerIsRegistered = false; @Override … Read more
This example will show you back navigation which is expected generally in most of the flows. You will have to add following code to every screen depending on expected behavior. There are 2 cases: 1. If there are more than 1 screen on stack, device back button will show previous screen. 2. If there is … Read more
Your problem is caused by back-forward cache. It is supposed to save complete state of page when user navigates away. When user navigates back with back button page can be loaded from cache very quickly. This is different from normal cache which only caches HTML code. When page is loaded for bfcache onload event wont … Read more