-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
fix(transition): reflow before leave-active class after leave-from (#2593), while fixing (#10688) #12288
Conversation
Size ReportBundles
Usages
|
Could you please add a test case for this to avoid regression? |
@vue/compiler-core
@vue/compiler-dom
@vue/compiler-ssr
@vue/compiler-sfc
@vue/reactivity
@vue/runtime-core
@vue/runtime-dom
@vue/server-renderer
@vue/shared
vue
@vue/compat
commit: |
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
Not entirely sure how to go about it, but I will try. |
…before *-leave-active
I'm not sure if this is really the best way, because it required me to modify the transition.html file and add a new function in e2eUtils.ts. I couldn't think of an easier and less intrusive way to check for reflow reliably. Maybe it's possible to do so with just classes, but I tried that multiple times with no success. |
LGTM. |
Just adding a few lines into the new test actually would be enough, I think, but I'm not sure if the current behavior is really the best, because right now the v-leave-from class will not give any visual results without a reflow in case of a cancelled enter transition, so I would say it's redundant. And since there is a dedicated |
Fixes an old issue (#2593) that was introduced again by commit 65109a7 while retaining the new functionality of the fixed issue (#10688).
Maybe the v-leave-from class should just not be added at all if the enter transition is cancelled? This should be more looked into.