-
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
fix(Popup): update offsets computations #13002
Conversation
@@ -13,7 +13,7 @@ const popupContentStyles: ComponentSlotStylesPrepared<PopupContentStylesProps, P | |||
pointerEvents: 'none', | |||
...getContainerStyles({ | |||
placement: p.basePlacement, | |||
margin: v.pointerMargin, | |||
padding: v.pointerMargin, |
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.
It's actually padding. Decided to keep variable's name to avoid breaking changes
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
Perf tests with no regressions
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: aa2d3f52cfc21c8c15e87e46947f43c2249339b2 (build) |
…/microsoft/fluentui into fix/popup-padding
…/microsoft/fluentui into fix/popup-padding � Conflicts: � packages/fluentui/CHANGELOG.md
Pull request checklist
Description of changes
In #12577 I fixed sizes of pointers, but during Popper update (#12530) I missed this update. I checked the issue and we should include
padding
when we are computing offsets. It's annoying that Screener can't catch such issues 👎Before
After
(with
pointerMargin: pxToRem(20)
)(with
pointerMargin: pxToRem(30)
)Focus areas to test
(optional)
Microsoft Reviewers: Open in CodeFlow