-
-
Notifications
You must be signed in to change notification settings - Fork 191
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
Update polyfill.js for browsers with poor support #277
Comments
For those not aware, the original maintainers of the project have not been able to be very active of late. I came on board with an interest in helping bring the Node implementation up to speed. This could have potential gains for the browser (and it should in Chrome and Safari 10+ if using the shim, though the shim is less necessary and still in need of having those theoretically more surmountable test failures fixed that are not failing in the Node implementation). However, as my interest and focus has not been on Either we need:
I know the latter is not very satisfying, especially since the largest base of users was using this for browsing polyfilling (the Node.js support was only added to |
Ok, so the plan is now to abandon |
Although this issue may tie in to all of the browser-specific (Safari) issues (hopefully all resolvable for Milestone 3.0.0 (tracking in #262)), I think it should be helpful for us to have a specific issue for tracking the updating of
polyfill.js
, as that file for browsers with poor support likeSafariIE has fallen majorly behind compared to the complete browser shim (and Node), including for newly added APIs likegetAllKeys
and such.The text was updated successfully, but these errors were encountered: