w3c / resource-timing

Resource Timing
https://w3c.github.io/resource-timing/
Other
119 stars 35 forks source link

sendBeacon() integration #377

Open annevk opened 1 year ago

annevk commented 1 year ago

According to https://bugs.webkit.org/show_bug.cgi?id=177579 no browser implements this. This appears true in Chromium and WebKit.

  1. Load https://tests.caniuse.com/?feat=beacon.
  2. Once everything has loaded, run performance.getEntriesByType("resource").
  3. Observe no "beacon" entries in the result.
yoavweiss commented 1 year ago

^^ @noamr

noamr commented 1 year ago

Oh need to see if this was ever implemented, I don't remember what exactly I checked when porting this stuff to fetch/RT.

yoavweiss commented 4 months ago

Is it correct to say that the next steps here would be to add a WPT that verifies what implementations actually do, and then align the spec on that?

Since no user has complained about this, I'm guessing the use case for this is not very important (as by the time that the beacon is sent, it's too late to report on the beacon itself, unless you send another beacon to report on the previous one, ad infinitum)

annevk commented 4 months ago

That makes sense to me.