v-bind in CSS values are set after the component's element is already in the DOM
matej-svejda opened this issue · 5 comments
Vue version
3.4.35
Link to minimal reproduction
Steps to reproduce
Click on "Toggle show test component"
What is expected?
The component opens with padding set to 100 initially.
What is actually happening?
The padding is animated from 0 to 100.
System Info
No response
Any additional comments?
This happens because when the component is initially mounted, the v-bind variables aren't set yet. So if onMounted triggers a DOM layout recalculation, then the padding is set to 0, after which it is immediately set to 100, triggering the animation. This didn't happen in older versions (for example 3.4.21).
But there is a similar, probably related issue that happens 3.4.35 and in older versions like 3.4.21: in some cases (I was able to reproduce it using Teleport), mounted in directives can be executed after the component already exists in the DOM but before the v-bind variables are set. If mounted then triggers a DOM layout recalculation, the same animation issue can happen again. Here's the code to reproduce it.
Basically, it would make things a lot easier if there was a guarantee that the element isn't added to the dom before the v-bind values are set to their initial values.
I found this PR. I think it's probably due to the impact of moving functionality to onMounted in this change.
Can I participate in solving this problem?
@Procrustes5
PR welcome~
Thank you for the quick turnaround 🙂 But this doesn't seem to fix the case with directives and Teleport for which I provided the example (this one). At least I can still reproduce the problem when I switch to the latest commit for the Vue version on SFC Playground.
a workaround
mounted: el => {
// lets recalculate the layout
nextTick(()=>{
console.log(el.getBoundingClientRect())
})
},@edison1105 Thanks, I'm aware of the workaround. It unfortunately doesn't work for my specific case.