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
The Javascript session will struggle to continue it’s mission in the face of impending doom. Coding in this manner is considered unpredictable. …and cruel.
I think I’ve found the solution, in the PhoneGap Application Delegate .m file {YourProject}AppDelegate.m, modify the method: – (BOOL)webView:(UIWebView *)theWebView shouldStartLoadWithRequest:(NSURLRequest *)request navigationType:(UIWebViewNavigationType)navigationType { return [super webView:theWebView shouldStartLoadWithRequest:request navigationType:navigationType]; } with – (BOOL)webView:(UIWebView *)theWebView shouldStartLoadWithRequest:(NSURLRequest *)request navigationType:(UIWebViewNavigationType)navigationType { NSURL *url = [request URL]; if ([[url scheme] isEqualToString:@”http”] || [[url scheme] isEqualToString:@”https”]) { return YES; } … Read more
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
window.open( ‘https://support.wwf.org.uk/earth_hour/index.php?type=individual’, ‘_blank’ // <- This is what makes it open in a new window. );
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