The pdf.js support range request. In fact it is doing range request right now, sending request from the beginning chunk by chunk (a set of bytes). But, it does not send request for the chunks of the current page. So in order to render current page, it have to loading from the beginning, which is rather slow. Besides, when it reach current page, it does not stop, but continue loading. This may cost too much memory for the browser, especially mobile device.
The pdf.js support range request. In fact it is doing range request right now, sending request from the beginning chunk by chunk (a set of bytes). But, it does not send request for the chunks of the current page. So in order to render current page, it have to loading from the beginning, which is rather slow. Besides, when it reach current page, it does not stop, but continue loading. This may cost too much memory for the browser, especially mobile device.