We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According the the Angular core Slack, there is an issue in some browsers when trying to call Symbol.for. Namely in Safari 8 and all versions of IE.
Symbol.for
I haven't reproduced this yet, but I can see/understand where the issue is. Such is the danger with DIY polyfills.
You can see that Symbol is supported in more browsers than Symbol.for is.
The text was updated successfully, but these errors were encountered:
It seems to be the same problem as #988.
Sorry, something went wrong.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
benlesh
Successfully merging a pull request may close this issue.
According the the Angular core Slack, there is an issue in some browsers when trying to call
Symbol.for
. Namely in Safari 8 and all versions of IE.I haven't reproduced this yet, but I can see/understand where the issue is. Such is the danger with DIY polyfills.
You can see that Symbol is supported in more browsers than Symbol.for is.
The text was updated successfully, but these errors were encountered: