I always use window.location in my code for two principal reasons: It’s a good habit to avoid global variables whenever possible. Using the window. prefix reminds me that the variable is global and that others aren’t. The nature of Javascript’s scoping allows you to override variables set higher up the scope tree. This means that … Read more
Using window.location.assign(“url”) will just cause a new document to load. Using window.location.replace(“url”) will replace the current document and replace the current History with that URL making it so you can’t go back to the previous document loaded. Reference: http://www.exforsys.com/tutorials/javascript/javascript-location-object.html
According to the W3C, they are the same. In reality, for cross browser safety, you should use window.location rather than document.location. See: http://www.w3.org/TR/html/browsers.html#dom-location
Try to use: location.reload(true); When this method receives a true value as argument, it will cause the page to always be reloaded from the server. If it is false or not specified, the browser may reload the page from its cache. More info: The location object
According to the W3C, they are the same. In reality, for cross browser safety, you should use window.location rather than document.location. See: http://www.w3.org/TR/html/browsers.html#dom-location
Solving this problem is much more within reach nowadays. The HTML5 History API allows us to manipulate the location bar to display any URL within the current domain. function removeHash () { history.pushState(“”, document.title, window.location.pathname + window.location.search); } Working demo: http://jsfiddle.net/AndyE/ycmPt/show/ This works in Chrome 9, Firefox 4, Safari 5, Opera 11.50 and in IE … Read more
window.open( ‘https://support.wwf.org.uk/earth_hour/index.php?type=individual’, ‘_blank’ // <- This is what makes it open in a new window. );