I am using Export to Excel component in our application and noticed that the exporting to excel is not working when the browser has pop up blocker extension enabled.
The same worked when testing locally but when deployed to a server with angular prod build then this scenario is produced.
I am able to download the file with the same build in Edge browser and Chrome Incognito.
I just checked the sample at https://www.infragistics.com/products/ignite-ui-angular/angular/components/exporter-excel#angular-excel-exporter-example and there also I am able to reproduce the issue.
I was expecting atleast a notification of blocking a file to be downloaded but that doesn't happend and I can see a console error as follows:
Failed to load resource: net::ERR_BLOCKED_BY_CLIENTcontent.index.js:2 Uncaught (in promise) TypeError: e.find is not a function at ntfShowManager_NtfShowManager.checkIsHidden (content.index.js:2) at content.index.js:2
Please let us know about the solution in this case.
Thank you for posting a question in our forum.
We are now looking into it. As it is likely it will take some more time, could you wait for a while?
Thank you in advance.
Thanks for the response. We are aiming to put this change in production very soon. So hopefully would expect a solution to this ASAP. Please let me know the status or if you want me to create a support case from my account?
You are seeing this error because Excel exporting process is getting blocked by that pop up blocker extension.
Unfortunately, this is not something that our product can control.
You will need to either disable/uninstall the popup blocker extension or choose other browsers in order to make the Excel exporter work.
I understand that it is getting blocked by that pop up blocker but the same export service is working fine with local angular build. It is only causing problem with production angular build I feel it can be fixed at your end.
Please check with the development team and see if that can be fixed. Otherwise let us know we will find another way to handle this scenario.
Hello Rameez,I have spoken with our development team regarding this issue. They say the reason why the popup blocker behaves differently is because all popup blockers have a list of whitelisted domains. If local builds are not being blocked by the popup blocker, then this means that localhost is among the whitelisted extension domains. So again it is basically beyond our control and is not something that can be fixed at our product level.