Excellent analysis by Henry as usual, can we find someone to pick up from here?
Too many duplicates here even if we subtract some which may not be directly related.
In terms of UX, this can cause considerable annoyances / inefficiencies for daily routines depending on users overall setup/preferences (between TB, browser, external apps).
(In reply to Henry Wilkes [:henry] from comment #0)
> Also get the printed error message
>
> ```
> JavaScript error: resource://pdf.js/PdfStreamConverter.jsm, line 140: TypeError: can't access property "getInterface", requestor is null
> ```
Error still seen in 98.0a1 (2022-01-21) (64-bit), Win10:
```
TypeError: can't access property "getInterface", requestor is null PdfStreamConverter.jsm:140:13
getDOMWindow resource://pdf.js/PdfStreamConverter.jsm:140
onStopRequest resource://pdf.js/PdfStreamConverter.jsm:1281
```
Excellent analysis by Henry as usual, can we find someone to pick up from here?
Too many duplicates here even if we subtract some which may not be directly related.
In terms of UX, this can cause considerable annoyances / inefficiencies for daily routines depending on users overall setup/preferences (between TB, browser, external apps).
(In reply to Henry Wilkes [:henry] from comment #0) //pdf.js/ PdfStreamConver ter.jsm, line 140: TypeError: can't access property "getInterface", requestor is null
> Also get the printed error message
>
> ```
> JavaScript error: resource:
> ```
Error still seen in 98.0a1 (2022-01-21) (64-bit), Win10: ter.jsm: 140:13 //pdf.js/ PdfStreamConver ter.jsm: 140 //pdf.js/ PdfStreamConver ter.jsm: 1281
```
TypeError: can't access property "getInterface", requestor is null PdfStreamConver
getDOMWindow resource:
onStopRequest resource:
```