New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Feb 2018
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug

Blocked on:
issue 695939

Sign in to add a comment

Issue 711060: sendBeacon does not add entries to ResourceTiming

Reported by, Apr 12 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3069.0 Safari/537.36

Steps to reproduce the problem:
1. navigator.sendBeacon(url, "")
2. Wait until the beacon is sent
3. performance.getEntriesByType("resource")

What is the expected behavior?
I would expect the sendBeacon() beacon to be in ResourceTiming

What went wrong?
No entries are added for sendBeacon()

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 59.0.3069.0  Channel: canary
OS Version: OS X 10.12.3
Flash Version: 

Note that fetch() seems to work correctly -- it adds a ResourceTiming entry.
500 bytes View Download

Comment 1 by, Apr 13 2017

Labels: Needs-Triage-M59

Comment 2 by, Apr 13 2017

The ResourceTiming entry does appear in FF 53

Comment 3 by, Apr 17 2017

Labels: -Needs-Triage-M59 M-60 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the isue on Mac-10.12.4, Windows-7 and Linux Ubuntu-14.04 using chrome stable version 57.0.2987.133 and canary 60.0.3072.0.
This is non-regression issue, observed from M40 #40.0.2172.0 and marking it as Untriaged to get more inputs from dev team.
Note:From M30 to M40 builds prompt doesn't appereared.


Comment 4 by, Jun 5 2017

tyoshino could you triage for sendBeacon?
This seems similar to issue with PerformanceObserver
Would it make sense to manually invoke FrameFetchContext::AddResourceTiming() as you indicated in this other bug?

Comment 5 by, Jun 6 2017

Components: Blink>Network
Owner: ----
Status: Available (was: Untriaged)

Comment 6 by, Jun 6 2017

Yes, calling FrameFetchContext::AddResourceTiming() properly for sendBeacon would fix this as well as  bug 665094 .

Comment 7 by, Jun 6 2017

Blockedon: 695939

Comment 8 by, Sep 7 2017

Components: Blink>PerformanceAPIs>ResourceTiming

Comment 9 by, Sep 7 2017

Components: -Blink>PerformanceAPIs

Comment 10 by, Feb 28 2018

Status: Fixed (was: Available)
The repro provided in the description now works.
Marking fixed.

Sign in to add a comment