-
Notifications
You must be signed in to change notification settings - Fork 523
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
How about we move the polyfill out? #433
Comments
We can create a new repo for the polyfill under w3c if needed. @philipwalton would you be willing to be the maintainer? |
I think it's also worth discussing whether we should just freeze/archive the polyfill code and auto-close the polyfill issues, now that IntersectionObserver is supported natively by all major browsers. |
SGTM :) |
@szager-chromium, can we take this up again? i.e., close/freeze all the polyfill stuff? |
@marcoscaceres @szager-chromium I'm triaging all the issues currently - I think it makes sense to archive/freeze the polyfill once we go through them all. Some are valid (typo in code), but most appear to be old browser bugs that should be handled by native implementations now. My plan is to close those and we'll see where we're at (perhaps cut one last version). |
Thanks for the update and helping with this, @miketaylr! |
I had a chat with @emilio about this, and he agrees that we should just remove it from the repo. @philipwalton - any thoughts of where we should move this? Deleting it entirely without the ability to update npm for an emergency hotfix maybe isn't the best idea. But I'm not sure if anybody really wants to maintain this... maybe we move it to GoogleChromeLabs and archive it? |
I'm fine with moving it to GoogleChromeLabs and archiving it. We can work with folks on our OSS team to get the repo created. |
It might be good to move the polyfill out... then it makes it easier for us to manage spec issues and polyfill issues.
The text was updated successfully, but these errors were encountered: