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

Avoid new Set([iterable]) for thenables #14592

Merged
merged 1 commit into from
Jan 15, 2019

Conversation

aweary
Copy link
Contributor

@aweary aweary commented Jan 15, 2019

Fixes #14583

I wrote and deployed a small test app and verified that this fixes the issue outlined in #14583 in IE11 on Windows 8.

Fixes facebook#14583

Using `new Set([iterable])` does not work with IE11's non-compliant Set
implementation. By avoiding this pattern we don't need to require a Set
polyfill for IE11
@gaearon gaearon merged commit 0fc1547 into facebook:master Jan 15, 2019
@gaearon
Copy link
Collaborator

gaearon commented Jan 15, 2019

Hmm. Now that I merged it, I realized ideally you wouldn't read field twice. Create a set, add the item, then set workInProgress.updateQueue. Mind tweaking?

jetoneza pushed a commit to jetoneza/react that referenced this pull request Jan 23, 2019
Fixes facebook#14583

Using `new Set([iterable])` does not work with IE11's non-compliant Set
implementation. By avoiding this pattern we don't need to require a Set
polyfill for IE11
n8schloss pushed a commit to n8schloss/react that referenced this pull request Jan 31, 2019
Fixes facebook#14583

Using `new Set([iterable])` does not work with IE11's non-compliant Set
implementation. By avoiding this pattern we don't need to require a Set
polyfill for IE11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

16.8.0-alpha.0 (and 16.7) IE11 Suspense doesn't stop rendering fallback after Lazy resolves
4 participants