Closed
Bug 1679737
Opened 5 years ago
Closed 1 year ago
Align resource timing's transferSize with the revised specification
Categories
(Core :: DOM: Performance APIs, defect, P2)
Core
DOM: Performance APIs
Tracking
()
RESOLVED
WORKSFORME
| Performance Impact | none |
People
(Reporter: annevk, Unassigned)
References
Details
(Keywords: sec-want)
As per https://github.com/w3c/resource-timing/issues/238 Safari does not expose it and it's a security issue.
|
||
Updated•5 years ago
|
Whiteboard: [qf-]
|
Reporter | |
Comment 1•5 years ago
|
||
Instead of not exposing it the specification changed to make the header size portion of this attribute a constant across all responses. This eliminates the security issue.
|
|
Reporter | |
Updated•5 years ago
|
Summary: Consider disabling resource timing's transferSize → Align resource timing's transferSize with the revised specification
|
|
||
Comment 2•5 years ago
|
||
marked for H2 WPT work 20201
|
||
Updated•4 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-]
|
||
Updated•4 years ago
|
Component: Performance → DOM: Performance
|
||
Updated•4 years ago
|
Severity: -- → S3
Priority: -- → P3
|
||
Updated•1 year ago
|
Priority: P3 → P2
|
|
||
Comment 3•1 year ago
|
||
It looks like this is fixed now after bug 1800443: https://searchfox.org/mozilla-central/rev/584b344830aa2558985675b99aaadbb915402caa/dom/performance/PerformanceResourceTiming.h#156-165
Closing.
You need to log in
before you can comment on or make changes to this bug.
Description
•