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
If the datepicker is loaded into the DOM, it already exists out of more than 70 DOM-nodes. Therefor if a lot of datepickers are rendered on screen, the UI becomes very laggy.
Expected Results
These DOM-nodes should only be rendered when the datepicker is open.
Actual Results
Only render the datepicker when it is open.
Other Information (e.g. stacktraces, related issues, suggestions how to fix)
/
The text was updated successfully, but these errors were encountered:
jocoone
changed the title
react-datetime renders way to much html elements without a reason
react-datetime renders to much html elements without a reason
Aug 19, 2019
jocoone
changed the title
react-datetime renders to much html elements without a reason
react-datetime renders too much html elements without a reason
Aug 19, 2019
Thanks for raising the issue. The rendered calendar is needed in case we wanted to animate when the calendar opens or closes. But it's true that we don't need the whole picker with its content to start the animation, so probably we can render only the container. That would be an enhancement.
I'm Submitting a ...
Steps to Reproduce
If the datepicker is loaded into the DOM, it already exists out of more than 70 DOM-nodes. Therefor if a lot of datepickers are rendered on screen, the UI becomes very laggy.
Expected Results
These DOM-nodes should only be rendered when the datepicker is open.
Actual Results
Only render the datepicker when it is open.
Other Information (e.g. stacktraces, related issues, suggestions how to fix)
/
The text was updated successfully, but these errors were encountered: