Use Uint8Array instead of Uint8ClampedArray for increased browser compatibility #12770
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
ahocevar
approved these changes
Sep 17, 2021
|
The Data Tiles example is now working on IE but I am unable to test the GeoTIFF example with Chrome 71 due to #12771 |
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.
As reported by @mike-000 in #12766, IE 11 and some Chromium browsers do not accept
Uint8ClampedArrayingl.texImage2D(). The issue has been fixed in Chromium, but we can useUint8Arrayinstead where we create 8-bit arrays that get passed as texture data for more compatibility.Closes #12766.