Expose some headers to fetch requests from the PDF.js Chrome extension #9447
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
movsb
pushed a commit
to movsb/pdf.js
that referenced
this pull request
Jul 14, 2018
Expose some headers to fetch requests from the PDF.js Chrome extension
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a work-around for https://crbug.com/784528 and allows the PDF.js networking code to perform more optimally. The user-visible effect is a visible progress bar, but this also affects file name determination and range request detection (which were broken because Chrome does not show these headers to callers of
fetch).Fixes #9446 (tested using the provided test case, step 1 & 2 = progress bar is visible)