-
-
Notifications
You must be signed in to change notification settings - Fork 231
@rc-component/trigger doesn't work with portals #434
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
Comments
@afc163 @zombieJ @MadCcc Can you please take a look at this issue and advise what you'd like to be done? To summarize, PR #412 (specifically the enabling of capture mode for the |
@linxianxi Could you look into this one? |
@linxianxi Can you please look at this issue? |
I have not used react-select and do not understand how it is implemented. |
@linxianxi
|
@linxianxi Did you have a chance to look at this problem? |
@afc163 What would you like to do with this issue? It doesn't seem like the person who created the PR that caused this regression is willing to address it.
|
I think this behavior is expected |
@linxianxi MUI is implemented in different way, there is a To allow the event reach the react-select in MUI, I set the height of mask to 200px. select.mp4 |
@linxianxi Can you please address @Ke1sy's comment? |
@afc163 What would you like to do with this issue? It doesn't seem like the person who created the PR that caused this regression is willing to address it. |
For current version, to resolve the case when outer use |
After update from v1.14.2 to v1.14.3 I noticed that @rc-component/trigger doesn't work good with portals as previously.

We use the react-select with portal inside the antd Table filter dropdown ([email protected]). Filter dropdown has the search value as well as "Filter" and "Clear" buttons.
To apply the filter user should select option and type search value and click "Filter". But we faced the issues with select (react-select) that uses portals after @rc-component/trigger was updated to v1.14.3 or higher.
Expected behaviour:
After selecting the option, the dropdown is not closed and user can continue set up the filter.
Codesandbox with v1.14.2:
https://codesandbox.io/s/filter-and-sorter-antd-5-10-0-forked-lygdxm?file=/demo.tsx
Actual behaviour:
After selecting the option, the dropdown is closed and user cannot continue set up the filter.
Codesandbox with v1.14.3:
https://codesandbox.io/s/filter-and-sorter-antd-5-10-0-forked-q6h9s9?file=/demo.tsx
We believe that this issue is caused by these changes 854325f.
CC: @mellis481
The text was updated successfully, but these errors were encountered: