Open
Bug 1679737
Opened 4 years ago
Updated 2 years ago
Align resource timing's transferSize with the revised specification
Categories
(Core :: DOM: Performance, defect, P3)
Core
DOM: Performance
Tracking
()
NEW
Performance Impact | none |
People
(Reporter: annevk, Unassigned)
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•4 years ago
|
Whiteboard: [qf-]
Reporter | ||
Comment 1•3 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•3 years ago
|
Summary: Consider disabling resource timing's transferSize → Align resource timing's transferSize with the revised specification
Comment 2•3 years ago
|
||
marked for H2 WPT work 20201
Updated•3 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-]
Updated•3 years ago
|
Component: Performance → DOM: Performance
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•