// Assuming the path is retreived and stored in a variable ‘path’ if (typeof(window.history.pushState) == ‘function’) { window.history.pushState(null, path, path); } else { window.location.hash=”#!” + path; }
To change the hash without having the page reload/scroll, you can now simply use html5 history.pushState. history.pushState(null,null,’#hashexample’); It’s supported by all the major browsers: http://caniuse.com/history MDN: https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/Manipulating_the_browser_history#The_pushState().C2.A0method Also note that the last url parameter we’re using here can be any url, so it’s not limited to hashes.
Can you try using document.location.replace() it is used to clear the last entry in the history and replace it with the address of a new url. replace() removes the URL of the current document from the document history, meaning that it is not possible to use the “back” button to navigate back to the original … Read more
It is just a SQlite 3 database, I was able to open it successfully (though of course you can’t open a locked database of a running browser).
history.back() should do the trick. window.history.back() documentation at MDN As an aside, it’s bad user experience if you do this unexpectedly on the user. For example, I enter in an invalid credit card number, and you take me back one page, instead of letting me fix the mistake. So while it’s possible to use javascript … Read more
after a while I found a reasonable workaround: in react, after every this.setState() I keep state synchronized with history using window.history.replaceState({ key: history.location.key, state: this.state}) when a “page” component is mounted or refreshed (willMount and willReceiveProps) I check for state in props.params.location.state: if there is one, I do restore it; if there is none I … Read more
So the bottom line is that iOS has added its own security around the history API, meaning that you can’t use script to change the url. Only a user action can allow the history API to change the url – i.e. a click – as per Aral’s example. The workaround is to uses a hash … Read more
I believe Sammy.js ( http://sammyjs.org) (MIT-licenced) has the best focus on what you want to do, with its 2 main pillars being: Routes Events I could quote from the docs but it’s pretty straightforward: setup clientside routes that relate to stuff to be done, e.g: update the view through ajax link events to call routes, … Read more
I think you have the right idea. I personally use .replace when redirecting from an invalid url (or non relevant, i.e. redirect to “profile” page when a logged user goes to the “/login” url), so using the browser’s “back” button works properly for the end user.