Datetime component is not removed from <body>
See original GitHub issueWhen we have one form with one or more datetime component each time that the form is rendered it adds one more <div class="flatpickr-calendar animate" tabindex="-1">...</div>
to <body>
After some time of use of the application we can have dozens (or even hundreds) of dummy divs.
This could be easily replicated in https://formio.github.io/angular-demo/manager
Is there anything we could on ngOnDestroy to release that when we navigate to out of the form?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
Datetime component is not removed from <body> #223 - GitHub
When we have one form with one or more datetime component each time that the form is rendered it adds one more <div ......
Read more >HTML5 datetime component is not working in browsers
The Ran the above code in IE(Edge). output is dispalying as simple test input. My guess, this datetime component is removed in all...
Read more ><input type="datetime-local"> - HTML - MDN Web Docs
This was available in the datetime input type, but this type is now obsolete, having been removed from the spec. The main reasons...
Read more >Is it possble to remove the time from the date picker?
In Microsoft's portal, for Date prompts in Request Offerings, only the date is available for selection. I'd like to mimic this in the ......
Read more >smart date time picker bug with reactive form patchvalue
If I run option (2) followed by option (3) then date value in the picker is NOT cleared to null and it still...
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
@Javo-blip This issue has been resolved in the latest version of 4x.
@Javo-blip Yes, please reopen a new ticket in the React issue board.
Thanks!