Describe the bug
keep router props history if page was loaded with passed props.
it was fixed here: 5ad3d8a (committed on Jan 20, 2023)
but it is still a bug when user swipe-back.
in other words: when user "go back" (router.back()), everything is ok (namely: router.propsHistory.pop();).
but when user swipe-back "it" doesn't "pop" propsHistory (which will cause a mess in route-props).
all we need is this line: router.propsHistory.pop(); (or router.propsHistory.length = router.history.length)
exactly right after this line:
Describe the bug
keep router props history if page was loaded with passed props.
it was fixed here: 5ad3d8a (committed on Jan 20, 2023)
but it is still a bug when user swipe-back.
in other words: when user "go back" (
router.back()), everything is ok (namely:router.propsHistory.pop();).but when user swipe-back "it" doesn't "pop" propsHistory (which will cause a mess in route-props).
all we need is this line:
router.propsHistory.pop();(orrouter.propsHistory.length = router.history.length)exactly right after this line:
framework7/src/core/modules/router/swipe-back.js
Line 265 in 3408af3