This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox version 44 won't work with a .aspx page but it did work with version 43.0.04

more options

We have a vendors site that we are able to create a .csv file for download. This is done through a .aspx file that has worked for the last 5 years. Today one of our computers updated to Firefox version 44.0 and it no longer will create the .csv file. We get no errors but it just doesn't create the file. All previous versions of firefox have worked.

We have a vendors site that we are able to create a .csv file for download. This is done through a .aspx file that has worked for the last 5 years. Today one of our computers updated to Firefox version 44.0 and it no longer will create the .csv file. We get no errors but it just doesn't create the file. All previous versions of firefox have worked.

All Replies (4)

more options

Firefox comes with some powerful Developer Tools, that should help you figure out why that no longer works. https://developer.mozilla.org/en-US/Learn/Discover_browser_developer_tools

more options

Has anyone on your team mentioned this problem to the vendor? Since ASP.Net code mostly runs server side, they probably will be able to debug the problem better than you can.

more options

We spoke with the vendor but there opinion is that this is a problem with Firefox. In there defense I would have to agree as IE, Safari both work fine. We have opted to switch back to IE rather than troubleshoot any further. Firefox 43.04 still work s fine on the computers that have not updated.

more options

Can you send the vendor the URL of this thread and ask them to point out the problem in Firefox, or have them file a bug in the tracking system (https://bugzilla.mozilla.org/)? Otherwise, it's not likely to get fixed.