Prevent "Uncaught promise" messages in the console when cancelling (some) ReadableStream
s
#13822
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.
While fixing issue #13794, I noticed that cancelling the
ReadableStream
returned by thePDFPageProxy.streamTextContent
-method could lead to "Uncaught promise" messages in the console.[1]Generally speaking, we don't really care about errors when cancelling a
ReadableStream
and it thus seems reasonable to simply suppress any output in those cases.[1] Although, after that issue was fixed you'd now need to set the API-option
stopAtErrors = true
to actually trigger this.