docs(engine): document missing motion engine keyframes with reproducible demo#55618
Conversation
✅ Submission Validation Passed!Great job! All required files are present and valid. 📁 Folder:
|
🎉 Congratulations on your PR merge, @broskell! 🚀Thank you so much for your valuable contribution to EaseMotion CSS! Your code is now merged into the main branch. 🎮 Join our Discord Server! ⭐ If you haven't already, please consider giving this repository a Star! It helps show your support, increases project visibility, and helps us grow the community. ✨ Thank you again, and happy coding! 💻 |
|
🎉 Pull Request Integrated! Thank you for your contribution, @broskell! Your changes have been successfully merged into 📊 Daily Merge Progress: You have merged 8/150 PRs today. Daily quota resets in 19 hrs. 📢 GSSoC Leaderboard Status Update: 🎮 Join our Discord Server! |
Summary
This PR adds a documentation submission that demonstrates and documents a gap in the current motion engine implementation.
The submission includes a reproducible demo highlighting several animation names accepted by the engine that currently have no corresponding keyframe definitions, making it easier for maintainers to verify and address the issue in a future core update.
Why
While exploring the motion engine, I noticed that several supported animation names can be parsed successfully but do not produce visible animations due to missing keyframe definitions.
Since contributors are only allowed to submit content inside the
submissions/directory, this PR provides a self-contained documentation example instead of modifying the framework itself.Contents
Added a new documentation submission:
The submission includes:
Notes
This PR intentionally does not modify any framework files.
It serves as a reproducible reference that maintainers can use when implementing the fix in the core library.
Testing
demo.html,style.css, andREADME.mdsubmissions/directoryChecklist
submissions/docs/