Scrolling quickly over popovers prevents removal from DOM about react-tiny-popover

[purplesquirrels]

Same issue for me too - invisible popovers are getting stuck on screen that can still be interacted with and block the content behind. I can't reproduce it consistently so I haven't been able to narrow down the circumstances when it is occurring. Seems like it may have something to do with the page scrolling while the popover is hiding? Mousing over and out doesn't hide it for me.

[djfariel]

Created a PR with a potential fix for this. Would appreciate if someone can tell me if this is the wrong approach to a solution. It feels hacky, but it works.
#56

[Louie-Healthsite]

@djfariel
I have possibly the same issue; moving the mouse over the popover content (away from target) does hide it, but it remains invisibly in the DOM i.e. not able to click components behind it

[jmbastidas]

Transition duration is the culprit, check: #61

Possible fix:

        if (!this.willUnmount || transitionDuration  > 0) {
            this.removePopoverTimeout = window.setTimeout(remove, (transitionDuration || Constants.FADE_TRANSITION) * 1000);
        } else {
            remove();
        }

As you can see remove is called after transitionDuration, sometimes callback is not called, some weird behavior is making setTimeout not calling the callback, there are libraries to replace setTimeout for something else which makes it to be always executed, the problem could be a combination of calling setState and few more things, but the final issue is that setTimeout is not reliable for some reason.
I don't really care about using transitionDuration, so zero is a value that will fix all problems if it can be supported.

Issue 61 has been sitting there for a some time, so we may need to live with our forks.

[alexkatz]

This should be fixed in version 6, which is a fairly substantial overhaul to the Popover component, now fully functional and hooks-based. Give it a look when you get the chance! I'll close this for now, but will reopen if the issue somehow reappears.