bug: [Bug in Ionic Vue Tabs Project]Clicking the buttons within the page fails to navigate to the page

[love-yukee]

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already report this problem, without success.

Ionic Framework Version

v8.x

Current Behavior

Hello, Ionic official. When I was using the Ionic framework to develop a Vue project, I encountered a rather troublesome bug. I created a tabs sample project. After clicking a certain Button on the page and using ionRouter to navigate to the second-level page, when refreshing this second-level page and clicking the Button again, I found that the page was stuck. However, the address in the address bar was correct and could not be clicked. This is one manifestation. The second manifestation is that on the second-level page, clicking a button to use windows.location.href = 'http://www.xx.com' to jump to an external link. After returning to the second-level page and then back to the first-level page, clicking the Button again will reproduce the first manifestation. But in the Tabs sample of Angular, this problem does not exist.

Expected Behavior

I hope the route navigation can jump normally.

Steps to Reproduce

1.Create a tabs sample project in the Ionic framework for Vue.
2.Click a Button on the first-level page to navigate to the second-level page using ionRouter.
3.Refresh the second-level page and try clicking the Button again.
4.On the second-level page, click a button to use windows.location.href = 'http://www.xx.com' to jump to an external link.
5.Return to the second-level page and then back to the first-level page.
6.Click the Button again.

Code Reproduction URL

https://gitee.com/FSAnoymous/ionic-vue-bug-demo

Ionic Info

6314ba5efb28e2cfccbc938282633495.mp4

97904832b5484a3564ee3c9f75d7360d.mp4

Additional Information

Sorry, my English is not very good. Please check the bug by looking at the performance in the video. This bug only exists in the Vue project, and there are no issues with the Angular demo. This has seriously affected the project experience. I hope it can be solved as soon as possible.