-
Notifications
You must be signed in to change notification settings - Fork 37
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
Comments
^^ @noamr |
Oh need to see if this was ever implemented, I don't remember what exactly I checked when porting this stuff to fetch/RT. |
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) |
That makes sense to me. |
According to https://bugs.webkit.org/show_bug.cgi?id=177579 no browser implements this. This appears true in Chromium and WebKit.
performance.getEntriesByType("resource")
.beacon
" entries in the result.The text was updated successfully, but these errors were encountered: