Breaks CSSTransitionGroup enter animations

[anthonator]

When using react-select I'm seeing enter animations breaking. They simply don't animate. The leave animations continue to work. If I remove the Select component from my view the animations start working again.

[VictorGarcia]

Any updates on this? I'm experiencing the same issue...

[B-Reif]

I'm having this issue too (almost a year later). I was able to restore the animation by setting searchable={false}.

Maybe the search input box is slowing down render times too much? Maybe this is related somehow to #733.

[mmellado]

Bump, experiencing this as well

[jjmr]

still happening after 3 years...any clue?

[jossmac]

Is this still an issue in v2?

[isakfagerlund]

Is this still an issue in v2?

This still happens in 2.1.0

[jossmac]

Could someone please provide a reproduction in CodeSandbox?

[bryant-sharethis]

same issue here

[gwyneplaine]

please feel free to reopen this with a codesandbox reproduction.

[foxinni]

It seems like isSearchable={false} for V2 fixes the CSS transition.

[OwenFlood]

I set up a quick codesandbox with both the searchable enabled and disabled to show the animation working/not working.

https://codesandbox.io/s/affectionate-rhodes-qir59

[twheys]

@gwyneplaine Could you please reopen this ticket given that @OwenFlood has posted a codesandbox link? This bug is still a thing.

[saltnpixels]

I made a useEffect that change the isSearchable to true after 1 millisecond....

const [isSearchable, setIsSearchable] = useState(false)
setTimeout(() => {
         setIsSearchable(true)
      }, 1)

But ultimately this needs a real fix....

[ebonow]

I set up a quick codesandbox with both the searchable enabled and disabled to show the animation working/not working.

https://codesandbox.io/s/affectionate-rhodes-qir59

I tested the link as provided, confirmed that this is indeed still an issue, and will reopen this.

@marianayap has been actively volunteering for issues and if she or anyone else would like to work on a fix and PR, then we can add this to the queue of PRs for release.

As an update to everyone, you can read more here, but...
TLDR: We've added collaborators and currently choosing PR candidates for v3.2.

[ebonow]

As expected, this appears to be an issue related to the AutosizeInput used in the Input component.

Here is a fork of the codesandbox example demonstrating the same behavior of AutosizeInput vs input here