Bug 235561 - ResourceTiming should have an entry when frames/iframes that change source
Summary: ResourceTiming should have an entry when frames/iframes that change source
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Frames (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-01-25 00:19 PST by Noam Rosenthal
Modified: 2022-02-01 00:20 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Noam Rosenthal 2022-01-25 00:19:07 PST 
When an iframe is loaded, it receives a ResourceTiming entry. however, when the src changes later, it doesn't receive a new one.
This was previously vague in the spec, new spec PR clarifies that when a frame navigation is container-initiated it should create an RT entry.

See https://github.com/whatwg/html/pull/7531 & https://github.com/w3c/resource-timing/issues/316
and WPT: https://github.com/web-platform-tests/wpt/pull/32490

Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1290721
Firefox behavior is according to the new spec addition.
Comment 1 Noam Rosenthal 2022-01-31 02:46:46 PST 
The same applies for frames/frameset: https://github.com/web-platform-tests/wpt/pull/32617
Comment 2 Radar WebKit Bug Importer 2022-02-01 00:20:16 PST 
<rdar://problem/88315662>