Bug 177579
| Summary: | Include "beacon" ResourceTiming entry | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Joseph Pecoraro <joepeck> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | achristensen, annevk, beidson, bugmail, cdumez, youennf |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Joseph Pecoraro
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Anne van Kesteren
I filed https://github.com/w3c/resource-timing/issues/377 to track this.