829d6ba2dc
When the end of data has already been reached for the various Streams, the `getByte` methods will return `-1` to signal that to the caller. Note however that the current position obviously won't be incremented in this case, meaning that the `peekByte` methods will in this case *incorrectly* decrement the position. Thankfully the corresponding `peekBytes` shouldn't be affected by this bug, since they decrement the current position with the *actually* returned number of bytes. I'm not aware of any bugs caused by this blatant oversight, but that doesn't mean this shouldn't be fixed :-) |
||
|---|---|---|
| .. | ||
| core | ||
| display | ||
| images | ||
| shared | ||
| doc_helper.js | ||
| interfaces.js | ||
| license_header_libre.js | ||
| license_header.js | ||
| pdf.image_decoders.js | ||
| pdf.js | ||
| pdf.worker.entry.js | ||
| pdf.worker.js | ||
| worker_loader.js | ||