Please reopen #3393

[tstriker]

Version

4.1.6

Reproduction link

github.com

Steps to reproduce

As the comments on the bug attest, vuejs/vue-router#3393 was closed prematurely and has been ignored since. I suspect the bug report was simply misunderstood.

The problem is that the watchers aren't dismounted before route change, causing unexpected side-effects.

Would it be possible to take another look at the bug and reopen it—otherwise users of vue-router have to come up with clunky workarounds.

What is expected?

Leaving state shouldn't trigger watchers

What is actually happening?

Watchers are triggered

[tstriker]

Ah, didn't realize the repos had been split up. Should i refile the bug with all the discussion from vuejs-router, or is this fine?

[posva]

A bug report requires a reproduction, so if you open a new issue, please provide one:

This looks related to some of these in Vue 3 so in this case could you try reproducing it using https://jsfiddle.net/posva/pdv8gmr7/ as a base but with Vue 2.7? If there is a bug, then open an issue on vuejs/vue. Thanks!