Closed DavidCPhillips closed 8 years ago
Reloads on history navigations (after a nav limit or error) always occur after the url has already been set to the new page. Typically this is not an issue, but if the url contains a hash, the browser ignores the call to 'window.location.href'.
For example. 1) Navigate to 'https://www.google.com/#foo' 2) Execute: window.location.href = 'https://www.google.com/#foo';
Nothing occurs. We probably need to follow the location.href change with a call to location.reload.
Reloads on history navigations (after a nav limit or error) always occur after the url has already been set to the new page. Typically this is not an issue, but if the url contains a hash, the browser ignores the call to 'window.location.href'.
For example. 1) Navigate to 'https://www.google.com/#foo' 2) Execute: window.location.href = 'https://www.google.com/#foo';
Nothing occurs. We probably need to follow the location.href change with a call to location.reload.