-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Bug/Feature: Datepicker - Callout dismisses when user picks a date #20638
Comments
@eivindland - thank you for filing this issue and apologies on the delay in reviewing the PR (#19798) associated to this issue. @spmonahan / @GeoffCoxMSFT - Could you please help out here? |
gouttierre
added
Component: DatePicker
Needs: Investigation
The Shield Dev should investigate this issue and propose a fix
and removed
Needs: Triage 🔍
labels
Jan 5, 2022
@eivindland can you confirm this is fixed in 8.50.0? |
spmonahan
added
Needs: Author Feedback
and removed
Needs: Investigation
The Shield Dev should investigate this issue and propose a fix
labels
Jan 21, 2022
Yes, I can confirm that this issue is fixed. Thanks! |
Fixed by #19798 |
Repository owner
moved this from Good Issues (High Priority)
to Done
in Fluent UI - Shield Priors
Feb 4, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Similar issue
There is a related issue already registered on Callout component. The pull request suggested would solve this Datepicker issue as well: #19797
Environment Information
Please provide a reproduction of the bug in a codepen:
Reproduction of the issue: https://codesandbox.io/s/fluentui-datepicker-9rlyo
The bug is in Callout, in dismissOnClickOrScroll which ev.target. It should read event's composedPath.
Expected behavior:
dismissOnClickOrScroll gets its target from ev.composedPath and properly calculates isEventTargetOutsideCallout.
Priorities and help requested:
Are you willing to submit a PR to fix?
This PR fixes the bug: #19798
Requested priority: Blocking -> We are unable to use Datepicker within our solution for now
The text was updated successfully, but these errors were encountered: