I am using ngx-extended-pdf-viewer version 20.2.0. The PDF viewer is attached to a mat dialog. Each time I open the dialog, ngx-extended-pdf-viewer creates a helper tag:
`
`
However, when the component is destroyed, this tag is not removed (not properly cleaned up). This isn't a big issue for 3 to 4 clicks, but in my case, I am using a legacy Bootstrap CSS package that overrides:
hidden input[type=file] {
display: block;
}
So this issue is clearly visible to me. I request that the temporary code be cleaned up when the component is destroyed.
As a temporary fix, I will override the CSS to hide the helper tag, but we need to ensure that the temporary code is cleaned up when the component is destroyed to prevent memory leaks.
same thing reproduced in the pdfviwer.net [Just switch multiple navigations and check dom]
I am using ngx-extended-pdf-viewer version 20.2.0. The PDF viewer is attached to a mat dialog. Each time I open the dialog, ngx-extended-pdf-viewer creates a helper tag:
`
` However, when the component is destroyed, this tag is not removed (not properly cleaned up). This isn't a big issue for 3 to 4 clicks, but in my case, I am using a legacy Bootstrap CSS package that overrides:
So this issue is clearly visible to me. I request that the temporary code be cleaned up when the component is destroyed.
As a temporary fix, I will override the CSS to hide the helper tag, but we need to ensure that the temporary code is cleaned up when the component is destroyed to prevent memory leaks.
same thing reproduced in the pdfviwer.net [Just switch multiple navigations and check dom]![image](https://github.com/stephanrauh/ngx-extended-pdf-viewer/assets/30429951/db68098a-f587-4bd6-a05a-ac2993fd55ce)
Thanks!
Version info
Version of ngx-extended-pdf-viewer: 20.2.0