motiondivision / motiondivision/motion

[BUG] ClipPath animation/effect fails to render on Chrome v151

Open
#3,786 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
33.7k
Forks
1.4k
Avg merge
1d 10h
Merged PRs (30d)
14

Description

Summary

The clipPath effect using Motion fails to execute or render properly in the latest Google Chrome update (Version 151.0.7922.76).
The code used to work fine, but after updating to this latest version of Google Chrome, I encountered this error.

Environment
  • Package: Motion V13.0.0 JavaScript
  • Browser: Google Chrome Version 151.0.7922.76
  • OS: macOS Tahoe V26.5
Expected Behavior

The element should smoothly animate its clipPath CSS property according to the defined motion properties.

Current Behavior

The clipPath effect does not transition smoothly. Instead, it stays locked at the initial value for the entire duration and then immediately jumps to the final value once the animation finishes.

Code
<style>
  .box {
    width: 150px;
    height: 150px;
    background-color: blue;
    margin: 60px auto;
  }
</style>
<div class="box"> </div>
<script src="https://cdn.jsdelivr.net/npm/motion@latest/dist/motion.js"></script>
<script>
const { animate } = Motion;
animate('.box', { clipPath: ['inset(0% 0% 0% 100% round 10px)', 'inset(0% 0% 0% 0% round 10px)'] }, { duration: 5 })
</script>

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the provided animate('.box', { clipPath: [...] }) reproduction in Chrome 151 and compare its behavior with an earlier browser version. Trace the clipPath animation path from the public animate API, then verify that the property interpolates smoothly throughout the five-second duration rather than jumping at the end.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, javascript, typescript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.