Firefox version 140browser update gives errors in web application when submitting form - ns_error_net_empty_response, and does not load js libraries - NS_binding_aborted
The issue is similar to the this"Firefox version 137 browser update gives errors in web application when submitting form - ns_error_net_empty_response, and does not load js libraries - NS_binding_aborted" But did not see any response for this issue.
Any solution as I am seeing this error only from firefox 140 esr verion prior to this it always worked for me. I checked for the solution related to " NS_binding_aborted" error on firefox but no luck did not find anything much.
I would highly appreciate for your support if you could find and tell me what is causing this error "NS_binding_aborted""on firefox 140. or else if you can tell me what is changed in firefox 140 version.
All Replies (2)
Hi there,
A couple of points that may help:
NS_BINDING_ABORTED is that in Firefox, a network request or resource load (like a JS file, image, or form submission) is cancelled before completing. This may happen when scripts or requests being interrupted by page reloads or redirects or third-party scripts that Firefox cancels if they don’t respond in time and especially add-ons or security software interfering.
Firefox 140 ESR there were updates to network and security layers, including stricter handling of fetch/XHR cancellations and better alignment with web standards. This means that requests which previously “failed silently” in older versions might now trigger visible errors like NS_BINDING_ABORTED.
Here are some things that may help!
Check the Console (F12 → Console/Network tabs) to see which requests are failing and whether they’re being blocked by CSP, CORS, or mixed content.
Test in Troubleshoot Mode (Menu → Help → Troubleshoot Mode) to rule out add-ons.
Try disabling Enhanced Tracking Protection for your web app temporarily and some scripts may be categorized as trackers.
If you have access to server logs, check whether requests are being dropped early (Firefox may now be stricter about timeouts or aborted connections).
If the issue persists, and especially if you can reproduce it consistently on Firefox 140 ESR but not 139 ESR, I recommend filing a bug at Bugzilla, so the developers can then confirm if this is a regression introduced in 140.
Modified by Shirmaya John
Tested and confirmed this issue does not exists 139 version of firefox .We are seeing this issue from 140version only.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.