This repository has been archived by the owner on Jan 20, 2024. It is now read-only.
Fixing TypeError: Invalid calling object in Edge #70
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
kyemelianov
approved these changes
Jul 18, 2018
This was referenced Jul 14, 2020
|
Closed via #150 |
|
The fix is now released in version 4.3.2. Thank you for the contribution! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I regret I was not able to reproduce the issue in automated tests. However, in my production project I observed TypeError 'Invalid calling object' in MS Edge when calling btoa. The same issue was raised in several projects, for example tus/tus-js-client#77. This change fixes the error.