When writing server-side code you need to explicitly stop execution after sending a "Location: ..." header to the client or your code will continue to execute in the background.
But what about when you change window.location in a client-side script? Does this immediately stop execution of the current script or is it up to the programmer to make sure that any code located after this call is not reached?
The window. location object can be used to get the current page address (URL) and to redirect the browser to a new page.
The window. location is read/write on all compliant browsers. The document. location is read-only in Internet Explorer but read/write in Firefox, SeaMonkey that are Gecko-based browsers.
Window stop() The stop() method is the same as clicking stop in the browser.
Setting window.location
does not implicitly stop JS execution. Take the following as an example:
function locationTest() {
window.location = 'http://www.google.com/';
window.open('http://www.yahoo.com/');
}
locationTest();
Try running that from Firebug/Web Inspector/etc. and you'll notice that the current window will load Google, but a new window will open with Yahoo as well.
Does this immediately stop execution of the current script
No, the remaining handler script will execute to the end before control returns to the browser and events start happening. When loading of the new page gets far enough for ‘navigation’ to occur, the beforeunload
and unload
events will fire, then the page and any script in it will become inactive.
However, any further queued events and timeouts might not fire. For example if you navigate the page in a click
handler of a form submit button and don't cancel the default action, it is possible (race condition) for the navigation to occur before the submit
event queued by the default action of the click
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With