RESOLVED WONTFIX 273295
decodedBodySize, encodedBodySize and transferSize are not populated with Timing-Allow-Origin * 
https://bugs.webkit.org/show_bug.cgi?id=273295
Summary decodedBodySize, encodedBodySize and transferSize are not populated with Timi...
alehm
Reported 2024-04-25 17:40:09 PDT
decodedBodySize, encodedBodySize and transferSize (tested only these) are not populated in PerformanceResourceTiming for cross origin requests with `Timing-Allow-Origin: *` http header set for both cached and non-cached resources. It works fine in Chrome and Firefox. See also https://w3c.github.io/resource-timing/#sec-cross-origin-resources.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2024-05-02 17:41:16 PDT
<rdar://problem/127466015>
Alex Christensen
Comment 2 2024-05-03 09:19:52 PDT
https://github.com/WebKit/WebKit/blob/main/Source/WebCore/page/PerformanceResourceTiming.cpp#L274 // This is intentionally stricter than a TAO check. // See https://github.com/w3c/server-timing/issues/89
alehm
Comment 3 2024-05-06 09:27:12 PDT
Thank you for your response. Is there a plan to implement https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-deliverytype? Otherwise, there is no way to find out whether a particular resource was loaded from the cache or not (without explicitly using Cache API or something similar).
Note You need to log in before you can comment on or make changes to this bug.