Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sendBeacon() integration #377

Open
annevk opened this issue May 3, 2023 · 4 comments
Open

sendBeacon() integration #377

annevk opened this issue May 3, 2023 · 4 comments

Comments

@annevk
Copy link
Member

annevk commented May 3, 2023

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
Copy link
Contributor

^^ @noamr

@noamr
Copy link
Contributor

noamr commented May 4, 2023

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
Copy link
Contributor

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
Copy link
Member Author

annevk commented Feb 28, 2024

That makes sense to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants