DayPicker height incorrectly set if element is hidden when rendered
See original GitHub issueI’m using DateRangePicker
, and the container I rendered it in had display:none
initially. This meant that when adjustDayPickerHeight()
was called, the calculated height was very small. When the container was then shown, the day picker retained this initial height and didn’t function correctly.
For now I’ve just made the component render when the container is shown, but it’d be good if this workaround wasn’t necessary 😃
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (2 by maintainers)
Top Results From Across the Web
DayPicker height incorrectly set if element is hidden ... - GitHub
I'm using DateRangePicker, and the container I rendered it in had display:none initially. This meant that when adjustDayPickerHeight() was ...
Read more >React Date Picker is Being Hidden Behind Overflow Parent ...
I have made my menu item the react datepicker input field. The issue is that my input field is the anchor for the...
Read more >Have a problem while making hidden <Div> element visible using ...
So what I do is, I hide the div element initially in CSS and make it visible ... <div style="height: 223px; width: 219px;...
Read more >LWC Datepicker in modal not displaying correctly
I've set the overflow: hidden; on the input element, and it solved the issue.
Read more >React custom datepicker: Step-by-step - LogRocket Blog
Set up a robust and attractive datepicker in React that acts as an alternative to the native HTML5 datepicker input element.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey, I am getting the same issue in “15.5.1”:
👆 same