-
Notifications
You must be signed in to change notification settings - Fork 47.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
Modern Event System: refactor legacy FB support logic #18336
Conversation
Details of bundled changes.Comparing: 1cf4a17...7cc9fca react-dom
Size changes (experimental) |
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 7cc9fca:
|
0f5e333
to
66f7c8d
Compare
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.
will stamp if you can clarify the comment about eventSystemFlags & LEGACY_FB_SUPPORT) === 0
, please and thanks!
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.
one last nit, but lgtm!
ea3ae21
to
7cc9fca
Compare
Modern Event System: refactor legacy FB support logic (facebook#18336)
This is a pretty big refactor of the FB event support logic in the modern event system. Previously, the logic worked for only Primer, but on more internal cases occuring, it seems we should probably delegated all "click" events to after the internal tooling runs, which fixes all the known issues with the legacy FB event systems. To ensure this works better, I've also made all the modern event system tests run with and without the internal FB flag so we catch more cases with this change.