-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RouterLink click.native handler stops being called after page rerender #12781
Comments
If load page async (https://codesandbox.io/s/angry-sun-y90on7?file=/src/main.js), then handler is never called |
You can use |
Are you only able to reproduce this with |
Only |
For what it's worth, I put together a reproduction in the Nuxt issue here, nuxt/nuxt#10593 (comment). I also went through the changes and confirmed this was working as intended on Vue 2.6.14 with both Vue Router versions ( That said, there is documentation on the proper way to utilize a Taking your example, @youngpirate32, here's a working version with the slot approach, https://codesandbox.io/s/nuxt-2-vue-2-7-click-event-bug-hzr4u4?file=/src/views/AboutView.vue. This also fixes the async version, https://codesandbox.io/s/nuxt-2-vue-2-7-click-event-bug-async-mqb3o3?file=/src/views/HomeView.vue. @yyx990803 though this does fix the issue, I'm still curious why the order of operation of click events previously supported All that to say that there is a valid, documented approach here that works to fix the issue, so this may not be a bug at all. Hope this helps! |
Hello. Is there any chance for it to be fixed? This is a huge regression actually, and the suggested workaround is not always suitable. Thank you. |
|
Version
2.7.10
Reproduction link
codesandbox.io
Steps to reproduce
What is expected?
The console will "on click" twice
What is actually happening?
In the console "on click" 1 time
The text was updated successfully, but these errors were encountered: