-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[Ref-Conformance] Adding a forwardRef to react-internal ContextualMenu #15625
[Ref-Conformance] Adding a forwardRef to react-internal ContextualMenu #15625
Conversation
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
Perf tests with no regressions
|
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 6e92f0d:
|
Asset size changes
Over Tolerance (1024 B) Over Baseline Below Baseline New Removed 1 kB = 1000 B Baseline commit: b14a4ed22b4ea4cd45fa09a4a34f9ccfe71d32dd (build) |
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.
Looks good, thanks!
microsoft#15625) * Adding a forwardRef to ContextualMenu * Adding a forwardRef to ContextualMenu * Updating ContextualMenu.base.tsx * Change files * Change files
…nously (#19122) PR #15625 moved the `hostElement` ref from an inner `div` of ContextualMenu, to the root `Callout` element. If the Callout component is loaded asynchronously, this can cause a crash when the ref doesn't refer to a fully loaded element. This change un-merges the `forwardedRef` and `hostElement` ref. It still applies the forwarded ref to the root Callout (to maintain the fix from #15625), but puts the `hostElement` ref back to the inner `div`.
…nously (microsoft#19122) PR microsoft#15625 moved the `hostElement` ref from an inner `div` of ContextualMenu, to the root `Callout` element. If the Callout component is loaded asynchronously, this can cause a crash when the ref doesn't refer to a fully loaded element. This change un-merges the `forwardedRef` and `hostElement` ref. It still applies the forwarded ref to the root Callout (to maintain the fix from microsoft#15625), but puts the `hostElement` ref back to the inner `div`.
Pull request checklist
$ yarn change
Description of changes
ContextualMenu
targetComponent
support to component-handles-refdefaultTest
disabledTests
from ContextualMenu.test.tsxFocus areas to test
ContextualMenu