[BUG] AnimatePresence with mode=popLayout doesn't consistently trigger opacity exit animations on elements with layout

[samselikoff]

2. Describe the bug

Motion elements with layout and exit animations don't always run their exit animations if they're inside an <AnimatePresence> that has a mode of "popLayout".

3. IMPORTANT: Provide a CodeSandbox reproduction of the bug

https://codesandbox.io/p/devbox/github/samselikoff/2023-11-25-framer-motion-pop-layout-bug/tree/main?file=%2Fapp%2Fpage.tsx%3A9%2C11

4. Steps to reproduce

Steps to reproduce the behavior:

1. Click the "Add item" 4 times
2. Click on an item. Notice it fades out.
3. Click another item. Notice it disappears (its exit opacity animation is not triggered)

Behavior seems to continue, where the fade-out only happens for every other item.

5. Expected behavior

Exit animation is always applied.

6. Video or screenshots

Screen.Recording.2023-11-25.at.10.25.14.PM.mov

[samselikoff]

Interestingly if I add a different prop to the exit animation, like x: 100, it seems to work. So might be some bug related specifically to opacity!

[RareSecond]

Am experiencing the exact same issue, but in a different setup. There seem to be cases where exit is never called, and the potential for it not being called seems to be indeed tied to opacity. If I remove the opacity on my exit, it will always get called.

Here's an example. If you slowly hover over the dots on the right, it works as expected. However, once you start going faster, it sometimes bugs and multiple divs remain visible

[quentinlagache]

Hey @mattgperry, Could you help or propose a workaround about this well documented issue from @samselikoff . We are also experiencing this issue in a lot of animations since 11.0.11 release.

[dclstn]

This bug is still prevalent, any updates or workarounds?

[iiskakov]

Can confirm, still an issue

[letelete]

@RareSecond can confirm. I faced a similar issue as described in #2416 (comment) recently. Have you found any workaround yet, by chance?

Tested on: "framer-motion": "^10.16.4"

[quentinlagache]

Bug since version 11.0.11.
Related issues: #2618 #2554 #2673

How can we help @mattgperry ?