-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[ClickAwayListener] Misc cleanup #20994
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have a preference on how to further cleanup the logic for v5?
Details of bundle changes.Comparing: b0d6b80...b2ea675 Details of page changes
|
The failing tests seem expected considering: https://caniuse.com/#search=composedPath. The end-user implication is that they will need to perform two interactions, one to remove the DOM node, a second one to trigger the click away. It seems to be an ok-ish degradation of the UX to save bundle size with the latest browsers. |
I think I'm ripping out |
No objection, the incentive for the |
I don't care. Too much work that'll be ignored later anyway. No idea why I relapsed. |
disableReactTree
from [ClickAwayListener] Fix support for portal #20406 (removed in [docs] Move more prop docs into IntelliSense #20342)