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
We recently updated to "ng2-pdfjs-viewer" version "18.0.0". After this update, we started encountering an error. We open the PDF viewer in a dialog window, and for the first time, it works correctly. However, when we open the dialog with the PDF viewer again, it starts throwing an exception. Eventually, it displays the PDF properly.
document-viewer.component.ts:18 TypeError: Cannot read properties of null (reading 'location')
at PdfJsViewerComponent.loadPdf (ng2-pdfjs-viewer.mjs:298:53)
at PdfJsViewerComponent.refresh (ng2-pdfjs-viewer.mjs:127:14)
at Object.next (document-viewer.component.ts:16:26)
at ConsumerObserver.next (Subscriber.js:91:33)
at SafeSubscriber._next (Subscriber.js:60:26)
at SafeSubscriber.next (Subscriber.js:31:18)
at Subject.js:34:30
at errorContext (errorContext.js:19:9)
at Subject.next (Subject.js:27:21)
Every time we open dialog with PDF viewer again, number of exception raise up:
After we refresh the page with F5, the first opening of the PDF viewer in dialog window is again without errors.
In the previous version, it was OK. Is anyone else encountering this issue too?
I am getting the same issue too. If this is not fixed soon, I will have to revert my upgrade and go back to the previous version. Does anyone know if the previous version is compatible with Angular 18?
Hi,
We recently updated to "ng2-pdfjs-viewer" version "18.0.0". After this update, we started encountering an error. We open the PDF viewer in a dialog window, and for the first time, it works correctly. However, when we open the dialog with the PDF viewer again, it starts throwing an exception. Eventually, it displays the PDF properly.
Every time we open dialog with PDF viewer again, number of exception raise up:
After we refresh the page with F5, the first opening of the PDF viewer in dialog window is again without errors.
In the previous version, it was OK. Is anyone else encountering this issue too?
Usage:
The text was updated successfully, but these errors were encountered: