Skip to content
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

Transition class leave-to not removed if hidden element changes too fast with v-show #7759

Closed
freakypie opened this issue Mar 6, 2018 · 5 comments
Labels

Comments

@freakypie
Copy link

Version

2.5.13

Reproduction link

https://jsfiddle.net/freakypie/nn2vwt7b/22/

Steps to reproduce

change a value in a vue really fast and the transition won't remove the leave-to class

What is expected?

the label should be shown

What is actually happening?

the label isn't shown


On my own app, i redirected to a page that was supposed to have no app header, but it then redirected to another page that did, but the header was missing anyway

@freakypie freakypie changed the title transition state inconsistent if value changes too fast Transition class leave-to not removed if hidden element changes too fast Mar 6, 2018
@posva posva changed the title Transition class leave-to not removed if hidden element changes too fast Transition class leave-to not removed if hidden element changes too fast with v-show Mar 6, 2018
@posva posva added the bug label Mar 6, 2018
@posva
Copy link
Member

posva commented Mar 6, 2018

As a workaround for the moment you can use a v-if instead of the v-show

@freakypie
Copy link
Author

freakypie commented Mar 6, 2018

for the moment i just debounced it and used a local property

    async "$store.state.invisible"() {
      clearTimeout(this.__updateInvisible);
      this.__updateInvisible = setTimeout(() => {
        this.invisible = this.$store.state.invisible;
      }, 50);
    },

that works for me, i just wanted to let you know about the bug

@jkzing
Copy link
Member

jkzing commented Mar 7, 2018

May be a dup of #5800 ?🤔

@posva
Copy link
Member

posva commented Mar 7, 2018

Oh, yeah, I didn't even check the code to see it was a v-show because it's a transition-group so I was expecting it to only do a v-for. Seems related but may be caused by different things, so I think we can keep it open for the moment

@yyx990803
Copy link
Member

This has been fixed by #7391 (not released yet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants