Make CORS errors errors, not warnings, in the console
Categories
(Core :: DOM: Security, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox73 | --- | fixed |
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
They're basically fatal errors for something the page is trying to do, so we should make them more prominent. This is not a "you might be doing something wrong, we think"; this is a "you tried to do something and it totally failed".
I looked into why they are warnings now, but that's just what they were in the initial commit in bug 713980.
|
Assignee | |
Comment 1•4 years ago
|
||
These typically indicate a fatal problem for whatever the page is trying to do;
we should give them the appropriate visibility.
|
||
Updated•4 years ago
|
Pushed by bzbarsky@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b6aa2fa7f967 Make CORS error messages be errors, not warnings. r=ckerschb
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
|
||
Updated•4 years ago
|
|
||
Comment 4•4 years ago
|
||
I believe we've always documented these as errors and not as warnings. See https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors for some material. I've mentioned this change on https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/73, though.
If there is any further docs update needed anywhere, let me know.
Description
•