Hey guys, patches below works fine for me :

diff --git a/lib/composables/router.js b/lib/composables/router.js
index fd42accc1674e85a542ca960e38676fd6878e2e5..3790ca4f5b3b9ec817f4907c138c2c1382703ec6 100644
--- a/lib/composables/router.js
+++ b/lib/composables/router.js
@@ -75,13 +75,25 @@ export function useBackButton(router, cb) {
   if (IN_BROWSER && router?.beforeEach) {
     nextTick(() => {
       window.addEventListener('popstate', onPopstate);
-      removeBefore = router.beforeEach((to, from, next) => {
+      removeBefore = router.beforeEach((to, from) => {
+        if (to === from) return;
+        const runCallback = () => {
+          let result;
+          const next = (val) => { result = val; };
+          if (popped) {
+            cb(next);
+            return result;
+          }
+          return undefined;
+        };
         if (!inTransition) {
-          setTimeout(() => popped ? cb(next) : next());
-        } else {
-          popped ? cb(next) : next();
+          inTransition = true;
+          return new Promise((resolve) => {
+            setTimeout(() => resolve(runCallback()));
+          });
         }
         inTransition = true;
+        return runCallback();
       });
       removeAfter = router?.afterEach(() => {
         inTransition = false;

@wusonw what do you think about my proposed change in this PR?
I also updated the typing of useBackButton function in the same file and the related packages/vuetify/src/components/VOverlay/VOverlay.tsx and packages/docs/src/main.ts.
Also added a few tests for useBackButton

When will this warning be fixed/removed?

@Elchin5757: When will this warning be fixed/removed?

rude 😛 I am sick now and do it for free anyway since OC funds dried up.

Can you download the repo, checkout this branch, build, point your app's package.json to the file:{path}/packages/vuetify, rebuild and verify it works fine in multiple scenarios (mostly dialogs and menus with persistent) while keeping in mind it was the not very reliable in the first place (#18505)? It genuinely would help even after merging this PR.

Tip: add { outline: '2px solid red' } to the styles below v-overlay__content in VOverlay.tsx to make sure your app loaded the local version. If you work with Nuxt, anytime you rebuild local vuetify, remove both node_modules and .nuxt and re-install dependencies.

It was to unit-test the useBackButton that was missing tests.
Let me remove them and try to add a test inside VDialog.spec.browser.tsx if possible.
If you have suggestions about the tests that needs to be performed, let me know, I will try to figure out something in the meantime

BTW, I think the issue in VDialog is out of the topic of this PR, I will try to investigate that in another PR right after this one, is that ok for you?

The current PR removes the deprecation warning in the console when using the next parameter in navigation guards from vue-router inside v-overlay components.

I know, they are used in VDialog, but also in VMenu, VOtpInput and others.

Hi, thanks for taking time to resolve the deprecation warnings. I would not mind unit-tests, but those were some kind of accidental nonsense that would only hurt us in the long run - by giving false confidence or failing for non-obvious reason. The more practical approach will be to have test for VDialog that are easy to grasp and repeat manually. You have proven the useBackButton can be broken in non-obvious way and I have spent hours on verification, so we will definitely benefit from the coverage.

If you can tackle any other outstanding issue with useBackButton, it would be of great help. Just prepare yourself to be questioned about the reason behind any changes in the code that are not 100% related to the problem 😉 If you got help from LLM-based tools, remember to trim, self-review and check the final output to avoid pushing slop with logical errors.

Warning gone after updating to the newly released v3.12.3

4e93846 landed in v3.12.3 Do you observe the warnings after the update?

Yes, it seems like it's fixed now! Thanks.