-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Always use sendBeacon instead of Image where available #2446
Comments
yes. Agreed. GA has an open bug where for sendBeacon requests, our servers respond before we get the full request and that has made us not go full sendBeacon. but overall, we would want to go full sendBeacon where possible. |
I don't fully understand: What does "our servers respond before we get the full request" mean? |
Is the proposal to change the |
Basically to kill the image transport and only use it if sendBeacon is not available. My main question is: Is there any reason not to do this? Does the image transport do anything that sendBeacon does not? |
|
Is @avimehta's latest response sufficient or does this need more discussion? |
If sendBeacon supported GET, would this allow us to make it the default for all browsers that support it? |
@igrigorik I'd think so. I can't think of any reason then not to use it as a default. |
Not going there until w3c/beacon#22 is resolved |
A proposal to implement this is here: #7096 |
Why would one ever want to use Image instead of sendBeacon?
I think we should always use sendBeacon if we can.
@avimehta @rudygalfi Any opinions?
The text was updated successfully, but these errors were encountered: