Usage with VelocityTransitionGroup gets the wrong position about react-popper HOT 3 CLOSED

Hi @souporserious! Sorry to ping you like this, but did you get a chance to look into this one?

from react-popper.

Instead of the repo, I changed this to a codesandbox for easier reproduction https://codesandbox.io/s/qvj9qov62w. I was thinking this might be the same kind of issue as #47, or there's something up with wrapping it in a <VelocityTransitionGroup /> (from https://github.com/twitter-fabric/velocity-react) that will make the positioning read out the offsets incorrectly? I'm not 100% sure how best to debug or how to force-schedule an update. Looking at the code, it looks like I won't be able to create my own applyStyle modifier either, as it's being disabled after spreading this.props.modifiers:

https://github.com/souporserious/react-popper/blob/ef520ee1213f30d3af3f10c6f5b4a04a888deb73/src/Popper.jsx#L96-L100

I tried adding my own computeStyle modifier, but that only broke things further, so I guess it was a naive and incomplete implementation of it. Hopefully the sandbox will make it easier to reproduce and help me figure out what's wrong here :)

from react-popper.

Sorry for the long wait on this. We expose a helper now to schedule an update when necessary. You should call this whenever a popper needs be replaced and might not have picked up the update.

from react-popper.