Bug 177579 - Include "beacon" ResourceTiming entry
Summary: Include "beacon" ResourceTiming entry
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-27 16:16 PDT by Joseph Pecoraro
Modified: 2023-05-03 08:17 PDT (History)
6 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 Joseph Pecoraro 2017-09-27 16:16:25 PDT 
Include "beacon" ResourceTiming entry.

The current Resource Timing spec expects beacon resource loads:
https://w3c.github.io/resource-timing/

Spec text:

> On getting, the initiatorType attribute must return one of the following DOMString values:
> ...
>     "beacon", if the request is the result of processing the sendBeacon method [Beacon];

Test:
1. Load https://tests.caniuse.com/?feat=beacon
2. Wait a while so beacons could be fulfilled
3. js> performance.getEntriesByType("resource")
  => No "beacon" entries

Notes:
- No other browser I tested included beacon loads in Resource Timing
- Note adding entries to the performance timeline exposes when the beacon was sent / response received. I don't think thats a bad thing.
Comment 1 Anne van Kesteren 2023-05-03 08:17:57 PDT 
I filed https://github.com/w3c/resource-timing/issues/377 to track this.