sendBeacon does not add entries to ResourceTiming
Reported by
nicjan...@gmail.com,
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.
,
Apr 13 2017
The ResourceTiming entry does appear in FF 53
,
Apr 17 2017
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. Thanks.
,
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? https://bugs.chromium.org/p/chromium/issues/detail?id=665094#c7
,
Jun 6 2017
,
Jun 6 2017
Yes, calling FrameFetchContext::AddResourceTiming() properly for sendBeacon would fix this as well as bug 665094 .
,
Jun 6 2017
,
Sep 7 2017
,
Sep 7 2017
,
Feb 28 2018
The repro provided in the description now works. Marking fixed. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ajha@chromium.org
, Apr 13 2017