Vue Wechat project page jump problem

vue single page project, developed by Wechat official account.
the front page is a list of information, which is returned by obtaining the official account in the background. The returned information contains a url that jumps to the details (only this url is returned in the background to jump to the details), in a format like this:

https://mp.weixin.qq.com/s?__.

but after opening through window.location.href in the project, the page jumps to the details and then jumps again, which is also the page. But there is a problem with the return at this time. You cannot return to the list unless you quickly click back twice to get to the list. I would like to ask what is the cause of this, and hope that experienced partners can support me.

in the development of this feature, refer to an official account called "Star teacher", their home page is also a list of official account articles, and then jump to the details can be returned normally, and later found that their details link is a short address, like this: https://mp.weixin.qq.com/s/vp..
and it is normal for me to try such a short address directly in my project. After jumping to the details, click back to return normally.

of course, whether it is a long address or a short address, if you open it directly through the browser, there is no problem, it will only jump, only in my project.

Does this have anything to do with the link address? Is there anything else that hasn"t been done on my side, or is it incorrect for the backend to provide url?

Thank you.

Jun.28,2021

before doing official account list crawling is also the kind of address at the back, and there is no problem to jump directly

I still feel that the address is different. Wechat will have some special treatment


there is "?" in the first address, Wechat will correct "?" The latter part is intercepted, so when the page is opened, you first open your own page, and then Wechat intercepts the url, and reopens the new url, so if you want to return normally, you need to "?" Get rid of it.


Thank you for your reply. The problem has been solved. Back-end colleagues deal with url

Menu