5 ms·
> To date, CORS network errors have been shown as warnings, making them too easy to overlook when resources could not load. Now they are correctly reported as e
by amenod 7y ago
> To date, CORS network errors have been shown as warnings, making them too easy to overlook when resources could not load. Now they are correctly reported as errors, not warnings, to give them the visibility they deserve.
I know this is a small improvement (s/warning/error), but like it nevertheless. What I would _LOVE_ however is that CORS errors would be displayed where it would make sense - in the Network tab. When I'm debugging connections I am looking there, not in Console.
- pedrogpimenta 7y agos/warning/error/g :)
- digitarald 7y agoFirefox dev here. Making sure failed requests are properly highlighted in Network panel is a big one on our list!
- RonanTheGrey 7y agoThis would be amazing. It's one of the last holdouts of why I develop on Chrome - I need to be able to see the failed request to debug what's getting sent and what isn't!
- amenod 7y agoVery glad to hear that! Now that I know what is going on, I check the console whenever the request doesn't appear in Network tab, but it is very unintuitive. Keep up the good work!
- Ayesh 7y agoNow that I'm reading this, I would love this feature! I like the network tab but debugging CORS or CSP with Firefox has never been so fun.
- amenod 7y agoActually in my experience Firefox CSP debugging is light years ahead of Chrome's. Not only debugging - CSP in Firefox at least works as intended, while with Chrome(ium) it's hit and miss. [0] That said, it does happen that Firefox gives a cryptic error message, and running in Chromium gives enough clues to solve the problem. But usually FF is much better with CSP, at least in my experience (and I work with CSP pretty often). [0] EDIT: "miss" meaning that the request, forbidden by CSP rules, is not stopped. Firefox correctly stops the same request.