Closed
Bug 1651006
Opened 5 years ago
Closed 5 years ago
Indicate that a response is not available to scripts
Categories
(DevTools :: Netmonitor, enhancement, P3)
DevTools
Netmonitor
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Honza, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug)
Attachments
(1 file)
|
10.79 KB,
image/png
|
Details |
image.png
This is a follow up for bug 1650844
STR:
- Open DevTools and select the Network panel
- Load http://odvarko.com/tests/network/cors/example4/
- Click the second button on the page (fetch not-shareable resource)
- Select the new (blocked) HTTP request and go to the Response panel
- The response body is visible, which is correct, but there should also be a notification explaining that the response body is not available to scripts (since blocked by CORS)
We already show a notification for broken JSON responses, so we can use the same UI.
See the attached mockup.
Honza
|
Reporter | |
Comment 1•5 years ago
|
||
Harald, how the message should look like?
Honza
Keywords: good-first-bug
|
|
Reporter | |
Updated•5 years ago
|
Flags: needinfo?(hkirschner)
|
||
Comment 2•5 years ago
|
||
Honza, is this good to close? or should we re-purpose for the headers panel notification?
Flags: needinfo?(odvarko)
|
|
Reporter | |
Comment 3•5 years ago
|
||
Yep, I am closing it.
Honza
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(odvarko)
Resolution: --- → WONTFIX
|
||
Updated•5 years ago
|
Flags: needinfo?(hkirschner)
You need to log in
before you can comment on or make changes to this bug.
Description
•