Closed
Bug 1934878
Opened 2 months ago
Closed 2 months ago
Data URIs should have a valid Size column in netmonitor
Categories
(DevTools :: Netmonitor, defect, P2)
DevTools
Netmonitor
Tracking
(firefox135 fixed)
RESOLVED
FIXED
135 Branch
Tracking | Status | |
---|---|---|
firefox135 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Since we reused the BiDi implementation for the data URIs support in DevTools, we currently have no size defined because this was postponed to followup Bug 1903807.
The issue is that it is not clear from a spec point of view if BiDi should set non-0 sizes here.
However for DevTools it probably makes sense to at least display a valid size in the corresponding column.
To do that we can fill the size
property of the response, without touching bodySize
and decodedBodySize
. WebDriver BiDi is not reading size
so it should be ok.
Assignee | ||
Updated•2 months ago
|
Assignee: nobody → jdescottes
Severity: -- → S3
Status: NEW → ASSIGNED
Priority: -- → P2
Updated•2 months ago
|
Blocks: netmonitor-columns
Regressions: netmonitor-columns
Updated•2 months ago
|
No longer regressions: netmonitor-columns
Assignee | ||
Comment 1•2 months ago
|
||
Set the response.text.length as response.size in NetworkObserver events for data URIs.
Fields used by WebDriver BiDi are not updated here. The existing data-uri test is updated in
order to check the size column.
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/24fff4275b89
[devtools] Set a valid size for data URIs requests in netmonitor r=devtools-reviewers,ochameau
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
status-firefox135:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•