Bug 235561
| Summary: | ResourceTiming should have an entry when frames/iframes that change source | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Noam Rosenthal <noam> |
| Component: | Frames | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | achristensen, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Noam Rosenthal
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Noam Rosenthal
The same applies for frames/frameset: https://github.com/web-platform-tests/wpt/pull/32617
Radar WebKit Bug Importer
<rdar://problem/88315662>