-
Notifications
You must be signed in to change notification settings - Fork 1
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
IE9ugh #3
Comments
haha i tried to get saucelabs working but i found their UI a clusterfuck. if you could get it working... 💃 i've tested it on safari and it seems to work. haven't tested on IE < 11 though since all i have is 11. be sure to not test the CDN version - they are usually outdated. i'll add you to the org and hopefully you can help. i can't do this all myself... haha |
Thanks for adding me. CI for this project would be huge so I'll definitely start there one way or another. How outdated is the CDN version? What's the actual update process for that? I've used a lot of what you've made/worked on and your continuos output is impressive. Seriously tho, I'd be impressed if you have a day job and don't just work on utility/consumable libs all day haha. |
i update the heroku instance. the CDN caches for 2 weeks or so, so it takes a while to update. AFAIK there's no way to invalidate, which is the problem. |
@jonathanong this is an awesome project. Would love to make this a required includes on all of my projects going forward and would love to help improve/extend/debug. It's silly to require individual polyfills when you should just be able to assume compatibility.
But for now I have had issues on certain browsers with the default script includes. Right now IE9 (fml) fails completely, but Safari also doesn't pass the test suite.
#2 is definitely a requirement and would love to help with that but I haven't had time to dive into this project yet to debug on my own, but when I get a chance I will definitely try to help/contribute. In the mean time, how would you prefer tracking individual browser issues?
The text was updated successfully, but these errors were encountered: