PDFDataRangeTransport appears to require 65536-byte chunks

[adammw]

I'm attempting to provide a custom transport which internally uses the fetch() api to grab the data from the PDF and therefore returns variable-sized chunks when reading. This doesn't seem to be documented anywhere, I just hitting this assertion, and I don't quite see how I can get this from PDFDataRangeTransport as it's used internally within the worker (or at least as far as I can tell). I can see a lot of issues from @bh213 about chunking/streaming PDFs, but that was back in 2014 so I'm not sure what the state of pdf.js is at the moment. Since PDF.js already has code to handle putting chunks together, it'd really help if the consumer of the API didn't have to do this, and PDF.js could just handle variable-sized chunks.

[timvandermeij]

I'm not sure if this will help you, but recently #6568 landed, allowing custom solutions to provide a range chunk size of their wish. Now that that is an API setting, it should make life easier for custom solutions, however since you want to have variable-sized chunks I'm not sure if it we be of much use for you.

[Snuffleupagus]

I'm attempting to provide a custom transport which internally uses the fetch() api to grab the data from the PDF and therefore returns variable-sized chunks when reading.

Note that the Fetch API has been officially supported for a couple of years now.
Furthermore, given #6517 (comment) and the age of the issue, should this be closed now?