Fix two issues encountered in Edge browser (#507) #508
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.
…ermining if a file has loaded, since in my testing, Edge is presenting a
File
object at this stage, rather than theBlob
that Chrome etc are presenting (fixes #507).If
createFileProcessorFunction
is presented with a file object that is not of typeBlob
(such asFile
, as seen in Edge browser), it attempts to iterate over it usingforEach
as if it were an iterable object, howeverFile
objects do not have aforEach
method. Resolve this by treating all file object input into this function as though they are a singular, non-iterable object (fixes [HAS PR #508] File not uploading in Edge browser, stalls at "Uploading" stage (no percentage) #507).Fix comment typo.