Skip to content
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/issue 291 #293

Merged
merged 4 commits into from
Jan 17, 2024
Merged

Fix/issue 291 #293

merged 4 commits into from
Jan 17, 2024

Conversation

afsalz
Copy link
Contributor

@afsalz afsalz commented Jan 16, 2024

Description

Type of change

  • Patch: Bug (non-breaking change which fixes an issue)
  • Minor: New feature (non-breaking change which adds functionality)
  • Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Docs: Documentation updates (if none of the other choices apply)

Checklist

  • Lint and unit tests pass locally with my changes.
  • I have added tests that prove my fix is effective or that my feature works.
  • I have tested my changes on the player-component and React player.

Copy link

changeset-bot bot commented Jan 16, 2024

🦋 Changeset detected

Latest commit: a74e762

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 11 packages
Name Type
@dotlottie/common Patch
@dotlottie/player-component Patch
@dotlottie/react-player Patch
next Patch
nuxt-app Patch
react Patch
vue Patch
web Patch
dotlottie-playground Patch
react-player-next Patch
react-player-test Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

github-actions bot commented Jan 16, 2024

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
packages/common/dist/index.js 7.45 KB (-0.07% 🔽) 149 ms (-0.07% 🔽) 179 ms (-17.01% 🔽) 328 ms
packages/player-component/dist/dotlottie-player.mjs 31.76 KB (+0.23% 🔺) 636 ms (+0.23% 🔺) 425 ms (+79.42% 🔺) 1.1 s

@afsalz afsalz requested a review from theashraf January 16, 2024 08:44
.changeset/wicked-bees-drum.md Outdated Show resolved Hide resolved
Comment on lines +1600 to +1608
// Fix: First loopComplete is not fired by lottie-web when direction is -1
if (this.currentState === PlayerState.Playing && this._loop && this._lottie.playCount === 0) {
this._lottie.triggerEvent('loopComplete', {
currentLoop: this._lottie.playCount,
direction: this.direction,
totalLoops: typeof this.loop === 'number' ? this.loop : Infinity,
type: 'loopComplete',
});
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if lottie-web fixes this issue from their end, would that make the loopComplete fire twice when playing in the reverse direction ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah it could fire twice. we may have to revert this change once they fix it.

@afsalz afsalz merged commit 871336a into master Jan 17, 2024
2 checks passed
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.

2 participants