-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Polyfill TypedArray.slice() in older browsers. fixes #11008 #11011
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kripken
wants to merge
3
commits into
main
Choose a base branch
from
slice
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that all of those actually have a super-class
TypedArray
that is not directly exposed. That is, instead of adding a method to each and every class, you can get aTypedArray
reference viaand then polyfill
typedArrayProto.slice
once.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, thanks, I didn't know that.
Do you know if that's well-supported in all legacy browsers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't, unfortunately, and can't test it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still relevant. In fact, we need these polyfills.
Tested this polyfill:
webOS 1.2 (WebKit)
Polyfill works correctly.
webOS 3 (Chrome 38)
Polyfill works, but
{}
getsslice
. So it is probably better to leave as it is.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dmitrylyzo thanks for the info. Would you like to open a PR that takes this code and updates it to use the right polyfills?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested your polyfill - works fine. As I said, I think it is better (for legacy browsers) than the super-class polyfill, because in webOS 3 super-class polyfill adds
slice
to every object due to a common prototype (but it could just be a glitch of the emulator).As for the other polyfills, they are for the libraries used in that project. Wouldn't their inclusion bloat the output file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I ask what targets do you have that run webOS 3 (chrome 38). That seems like a rather old version of the browser to target.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly old TVs (https://webostv.developer.lge.com/discover/specifications/web-engine/). Jellyfin is targeting Chrome 27 as a rough approximation of webOS 1.2 and 2.0 (both WebKit).