-
Notifications
You must be signed in to change notification settings - Fork 216
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
Issues in Chrome 65 #225
Comments
I'm getting similar behavior. I was able to properly download the file in Microsoft Edge 41.16299.15.0. |
Getting same concern. Please suggest how can we fix this issue in Chrome version 65.0.3325 |
@clebens, ng-csv also still works fine in Firefox too. |
https://github.com/dirwin517/ng-csv npm i ng-csv2 --save Is working for me, hopefully that helps |
@dirwin517 Thank you bud!! My users are going to be happy they don't have to run multiple browsers. Did you perhaps make a pull request for @asafdav to integrate the changes? |
thank you @dirwin517. It fixes Chrome 65 but breaks firefox (at least 59) :( |
Thanks for this @dirwin517 Noticed that there was a bug using this with IE that redirected to another page when downloading the csv. Will submit a PR for a fix I found for it. |
npm i ng-csv2 --save did not work for me. |
@Crash-- Have submitted a PR to @dirwin517 that should fix the issue with Firefox. |
It seems that ng-csv (this one) works again with Chrome 65. |
I'm still seeing the issue with Google Chrome Version 65.0.3325.181 (Official Build) (64-bit) on a MAC Cherry Picked changes into PR #226 |
thx @dirwin517 it's working again in Google Chrome |
Thanks dirwin. Its fixed in Chrome 65 Version but breaking in Firefox 52.7.3. |
It seems this is fixed in Version 66.0.3359.137 |
Hey there,
I'm not sure what has changed, but I'm not getting any errors, or any results in Google Chrome Version 65.0.3325.181 (Official Build) (64-bit).
It seems like it tries to open a new tab, and then the tab goes away instantaneously, but no file is downloaded. Any known workarounds?
The text was updated successfully, but these errors were encountered: