Skip to content

fix: tolerate rounding at adjacent keyframe boundaries - #205

Merged
dazzatronus merged 2 commits into
mainfrom
fix/keyframe-boundary-rounding
Sep 25, 2026
Merged

dazzatronus merged 2 commits into
mainfrom
fix/keyframe-boundary-rounding

Conversation

@dazzatronus

Copy link
Copy Markdown
Contributor

Valid adjacent animation segments can fail to load because 0.7 + 3.2 evaluates to 3.9000000000000004, slightly past the next segment at 3.9. Boundary normalisation can retain that rounding difference.

Apply the existing timing tolerance when rejecting overlaps. Genuine overlaps still fail validation. The regression test checks playback through the original decimal boundaries.

Verify: Node 22; all 30 keyframe and opacity tests pass, including genuine-overlap rejection.

@dazzatronus
dazzatronus merged commit 2c4e2c9 into main Sep 25, 2026
1 check passed
@dazzatronus
dazzatronus deleted the fix/keyframe-boundary-rounding branch September 25, 2026 00:59
github-actions Bot pushed a commit that referenced this pull request Sep 25, 2026
## [2.22.4](v2.22.3...v2.22.4) (2026-09-25)

### Bug Fixes

* restore timeline thumbnails after generation succeeds ([#204](#204)) ([75be088](75be088))
* show relevant help for timeline preview errors ([#206](#206)) ([51500d3](51500d3))
* tolerate rounding at adjacent keyframe boundaries ([#205](#205)) ([2c4e2c9](2c4e2c9))
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 2.22.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant