Skip to content

[6.x] Don't use motion-vue for bard/replicator set animations#13973

Merged
jasonvarga merged 4 commits into6.xfrom
sets-motion
Feb 18, 2026
Merged

[6.x] Don't use motion-vue for bard/replicator set animations#13973
jasonvarga merged 4 commits into6.xfrom
sets-motion

Conversation

@duncanmcclean
Copy link
Member

@duncanmcclean duncanmcclean commented Feb 17, 2026

This pull request removes the Motion component from Bard/Replicator sets to improve performance. Part of addressing #13385.

Fixes #13958

Before

CleanShot.2026-02-17.at.15.02.39.mp4

After

CleanShot.2026-02-17.at.14.59.22.mp4

@jasonvarga
Copy link
Member

Wouldnt the clip issue be on bard sets too?

@duncanmcclean
Copy link
Member Author

Actually, in chatting with Claude, I'm not sure we even need overflow-clip on replicator sets anymore.

overflow-clip was conditionally applied during Motion's height animation and removed after completion. Now that we're using v-show, there's no animation to clip during.

@Brewd3v
Copy link

Brewd3v commented Feb 18, 2026

I was experimenting with our project this morning and found the same. Replacing motion with a v-show div made it so much faster. Night and day.

@jasonvarga jasonvarga merged commit b9e2d63 into 6.x Feb 18, 2026
11 checks passed
@jasonvarga jasonvarga deleted the sets-motion branch February 18, 2026 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bard sets visually collapse and re-expand when nested field values change

3 participants

Comments