plans/issues/issue-2676.md
Executor instructions: Follow step by step; run the drift check first. Update the status row for this plan in
plans/issues/README.mdwhen done.Drift check (run first):
gh api repos/motiondivision/motion/issues/2676 --jq .state→ expect"open". If already closed, mark this plan DONE and stop.
42bfbe3ed, 2026-06-11Filed 2024-05-19: the CodeSandbox examples linked from the then-current docs
(e.g. the notifications example framer-motion-notifications-5cvo9, pinned to
framer-motion 1.1.0–6.5.1) behaved differently from the latest package.
Facts:
dev/react/src/examples/, dev/html/public/), which track workspace
versions automatically and are not what the issue refers to.Open plans/issues/README.md, find the issue-2676 row. If not APPROVED, mark
this plan BLOCKED and stop.
gh api repos/motiondivision/motion/issues/2676/comments -f body="Closing: the examples this refers to were CodeSandbox embeds in the old framer.com docs, which don't live in this repository. The documentation has since been rewritten at motion.dev with examples built against current versions of the library. If you spot a specific outdated or broken example on motion.dev today, please report that example directly. @malmz — the quick-swipe double enter animation you mention would be a library bug rather than a docs issue; if it still reproduces on motion@12, please open a new issue with a minimal repro."
gh api -X PATCH repos/motiondivision/motion/issues/2676 -f state=closed -f state_reason=not_planned
Verify: gh api repos/motiondivision/motion/issues/2676 --jq .state → "closed".
not_planned (only after APPROVED)plans/issues/README.md status row updated