Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reimplement non-conflicting fix for #53 #155

Merged
merged 1 commit into from
May 2, 2018
Merged

Conversation

xxx
Copy link

@xxx xxx commented Oct 27, 2017

I really need this fix, so here is a reimplementation of #74 that doesn't conflict. All credit goes to @stephen though.

@mikecx
Copy link

mikecx commented Apr 26, 2018

Super annoying that 6 months out this two line fix hasn't been merged in. Any chance this can be merged?

@denisftw
Copy link

denisftw commented May 1, 2018

@mikecx The project seems abandoned to me. Have you found a decent alternative?

@mikecx
Copy link

mikecx commented May 1, 2018

@denisftw Agreed, definitely looks dead. We're on the CatchRelease branch now but possibly looking to move to React Portal Popover as Portals are supposed to be used for this sort of thing.

@denisftw
Copy link

denisftw commented May 1, 2018

@mikecx Thanks, I didn't know about the CatchRelease fork. React Portal Popover doesn't look very active though. I was thinking of react-popper, but its API is definitely more complicated.

@jasonkuhrt jasonkuhrt merged commit 9d96f95 into jasonkuhrt:master May 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants