You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DateRangePicker has no way to close the dropdown using code. There are a couple of scenarios where it is needed:
When a user clicks outside the dropdown on an iFrame, the dropdown is not closed. This is a significant issue when most of the app is in an iFrame.
When DateRangePicker becomes disabled while the dropdown is opened. The dropdown stays open while the trigger button is disabled, and the user can apply a new range.
The issue might be valid for other controls with a dropdown.
Hello @apisarev ,
We apologies for not responding to you question in time!
That is something that our components with dropdowns should handle on blur. I couldn't easily reproduce the issue (date range picket dropdown got closed as expected), but we will look deeper. Did you check, if the issue happens for you for Select or Autosuggest components?
There is a work around, which isn't ideal, but can be a short-term fix. You can assign a key to the dropdown and reset it when clicking outside of the iFrame. That will trigger re-render and dropdown will be closed.
Disabling or changing controls when users are editing them is a design anti-pattern and creates a poor user experience. We discourage such behaviour.
That said, we do not have enough data to expose close() method for the dropdowns.
Description
DateRangePicker has no way to close the dropdown using code. There are a couple of scenarios where it is needed:
The issue might be valid for other controls with a dropdown.
Code of Conduct
The text was updated successfully, but these errors were encountered: