CSR-2183: avoid 'invalid navigation guard' by ensuring next() is always resolved
This commit is contained in:
parent
95c6e0c0aa
commit
15aaca73ac
1 changed files with 3 additions and 0 deletions
|
|
@ -268,11 +268,14 @@ router.beforeEach(async (to, from, next) => {
|
|||
if ((isInIframe && notToPIAReturn) || fromPaymentToConfirmation) {
|
||||
const newUrl = `${window.top.location.origin}${to.href}`;
|
||||
window.top.location.href = newUrl;
|
||||
next(false);
|
||||
|
||||
// Refresh page if navigating to self to prevent locking.
|
||||
// For now only carved out for vehicle; all modals are opened through anchor tags at the moment,
|
||||
// which also self navigate, but relied on the page remaining the same on self-navigation.
|
||||
} else if (toQueryPage === fromQueryPage && toQueryPage === getRedirectedStartPage()) {
|
||||
router.go(0);
|
||||
next(false);
|
||||
} else {
|
||||
next();
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue