-
-
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
custom event emit by the v-if component yet trigger the v-else component listener #7294
Closed
mqli opened this issue
Dec 21, 2017
· 1 comment
· Fixed by annict/annict#1034, annict/annict#1035, owncloud/web#46, OSM-Browser/osm-browser#56 or OSM-Browser/osm-browser#58
Closed
custom event emit by the v-if component yet trigger the v-else component listener #7294
mqli opened this issue
Dec 21, 2017
· 1 comment
· Fixed by annict/annict#1034, annict/annict#1035, owncloud/web#46, OSM-Browser/osm-browser#56 or OSM-Browser/osm-browser#58
Labels
Comments
Replaced the repro with a correct one (use the non minified version it warns you about problems) |
lovelope
pushed a commit
to lovelope/vue
that referenced
this issue
Feb 1, 2018
This was referenced Mar 14, 2018
f2009
pushed a commit
to f2009/vue
that referenced
this issue
Jan 25, 2019
aJean
pushed a commit
to aJean/vue
that referenced
this issue
Aug 19, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
2.5.13
Reproduction link
https://codepen.io/posva/pen/baeJzd?editors=1111
Steps to reproduce
define a custom component witch emit custom event;
use v-if v-else create 2 component instances;
on first instance use v-on listen the custom event, the second DONOT;
toggle the v-if condition;
emit the custom event on the second instance
What is expected?
the listener on the first instance not been triggered
What is actually happening?
the listener on the first instance been triggered
The text was updated successfully, but these errors were encountered: