-
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
Exposing IPopupProps on Panel #14868
Exposing IPopupProps on Panel #14868
Conversation
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 4834558:
|
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 d731cd8:
|
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Potential regressions comparing to master
Perf comparison
Perf tests with no regressions
|
Asset size changes
Over Tolerance (1024 B) Over Baseline Below Baseline New Removed 1 kB = 1000 B Baseline commit: 12e72defeec4e1c2a6c7326c9cef670f6c2b2a55 (build) |
🎉 Handy links: |
* expose and pass through popup props * Change files * actually a minor change * Remove header example * api updates
Pull request checklist
$ yarn change
Description of changes
There are times when the consumer may want to talk directly to the underlying Popup component, for instance when overriding default aria props assigned by the component. This change allows for that.
Focus areas to test
The component should remain functionally the same, but allow for the consumer to pass through PopupProps.