Bugzilla

(In reply to Jonas Jenwald [:Snuffleupagus] from comment #12)
> (In reply to Emilio Cobos Álvarez (:emilio) from comment #11)
> > Looks like a pdf.js issue where it doesn't unblock the load event. I can repro trivially.
> 
> That would suggest that all of the pages never load, which seems really weird to me.
> 
> > If you don't have the time let me know and I can investigate.
> 
> I'm guessing that testing this locally would require doing a "full build", rather than just an "artifact build", right?
> If so, then I'm sorry to say that I don't have time to test this unfortunately (being that I'm not employed by Mozilla).

Yeah, that makes sense, no worries :(

It doesn't quite need a full build, after looking a bit at it. That waiting function seems unused.

I can repro this just loading an empty (zero-size) file. So literally `touch foo.pdf`, then load it, the pages loaded promise won't resolve, nor reject. I'll poke more but if you have any ideas that'd be awesome of course :)

(In reply to Jonas Jenwald [:Snuffleupagus] from comment #12)
> (In reply to Emilio Cobos Álvarez (:emilio) from comment #11)
> > Looks like a pdf.js issue where it doesn't unblock the load event. I can repro trivially.
> 
> That would suggest that all of the pages never load, which seems really weird to me.
> 
> > If you don't have the time let me know and I can investigate.
> 
> I'm guessing that testing this locally would require doing a "full build", rather than just an "artifact build", right?
> If so, then I'm sorry to say that I don't have time to test this unfortunately (being that I'm not employed by Mozilla).

Yeah, that makes sense, no worries :)

It doesn't quite need a full build, after looking a bit at it. That waiting function seems unused.

I can repro this just loading an empty (zero-size) file. So literally `touch foo.pdf`, then load it, the pages loaded promise won't resolve, nor reject. I'll poke more but if you have any ideas that'd be awesome of course :)