Make scroll lock div work on a document context it belongs to

[aszmyd]

Fixes #5346

[changeset-bot]

🦋 Changeset detected

Latest commit: f313a13

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
react-select	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit f313a13:

Sandbox	Source
react-codesandboxer-example	Configuration

[lukebennett88]

Thanks for your PR @aszmyd.
Could you please create a CodeSandbox example showing the use case you're trying to solve. The code looks pretty straight forward, but I'd like to test it a little more 🙂
Also this PR will require a changeset in order to get merged. If you haven't used changesets before, instructions on how to do that are available here.

[aszmyd]

I've updated the branch, included the changeset, and prepared two CodeSandbox instances to show the issue:

• Sandbox running on react-select 5.7.4
• Sandbox running on commits from this PR - df685f08 - it doesn't include the commit with the changeset but its irrelevant to the code logic

I also recorded a small demo of the bug (link) - first part shows the behavior on the 5.7.4 version and second (on the second tab of the browser) shows the fix. The bug is that it's not possible to close the opened select by clicking outside of it when the menuShouldBlockScroll option is set to true.

I've used react-new-window package to make a new document context case (it simply opens a new popup window and uses React Portals to render component on it) as I'm using this package also in my current production codebase.

As mentioned in the issue description, the problem only occurs when the menuShouldBlockScroll is set tu true.

Please let me know if there is anything else I do to make this merged. Our application has no workaround for this bug and it's quite annoying for the our users currently.

Thanks

[lukebennett88]

Thanks so much for the PR, and for the thorough documentation and examples @aszmyd.
Everything looks good to me, so I'm going to approve and merge it.