Skip to content
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

fix: bring back Android 4.x support #6289

Merged
merged 5 commits into from
Nov 7, 2019
Merged

fix: bring back Android 4.x support #6289

merged 5 commits into from
Nov 7, 2019

Conversation

gkatsev
Copy link
Member

@gkatsev gkatsev commented Oct 28, 2019

If we are running on a browser that doesn't support WeakMap, use a
simple WeakMap sham as a fallback.
Also, add a tiny Set sham.

We received a request (in #6103) that we broke Android 4.x due to lack to WeakMap. This creates a WeakMap sham to use as a fallback when WeakMap isn't available.

To test locally, I change the file to always create the FakeWeakMap and use that as the default export.

If we are running on a browser that doesn't support WeakMap, use a
simple WeakMap sham as a fallback.
@gkatsev gkatsev changed the title fix: fallback to a simple WeakMap sham fix: bring back Android 4.x support Oct 29, 2019
@gkatsev gkatsev merged commit bacd2b2 into 7.6.x Nov 7, 2019
@gkatsev gkatsev deleted the weakmap-fallback branch November 7, 2019 21:35
gkatsev added a commit that referenced this pull request Nov 7, 2019
Use a WeakMap and Set shams for browsers that don't support it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants