We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Missing compatibility data
Both Chromium and Safari implement strict payload size limits on data sent via sendBeacon or fetch with keepalive: true.
This is really poorly documented across the web, and extremely difficult to diagnose.
Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Safari
A note in this article that many browsers impose strict size limits on beacon requests could have saved me days of investigation.
I spent the last several days investigating an issue that turned out to be a symptom of this behaviour.
To reproduce is pretty simple though, simply attempt to call sendBeacon in chrome with a request body larger than 64 kB.
navigator.sendBeacon("http://google.com", new Array(100000).join("Z"));
I found this comment buried in a w3c pull request that references the limitation:
w3c/beacon#39 (comment)
No response
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/sendBeacon
api.Navigator.sendBeacon
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What type of issue is this?
Missing compatibility data
What information was incorrect, unhelpful, or incomplete?
Both Chromium and Safari implement strict payload size limits on data sent via sendBeacon or fetch with keepalive: true.
This is really poorly documented across the web, and extremely difficult to diagnose.
What browsers does this problem apply to, if applicable?
Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Safari
What did you expect to see?
A note in this article that many browsers impose strict size limits on beacon requests could have saved me days of investigation.
Did you test this? If so, how?
I spent the last several days investigating an issue that turned out to be a symptom of this behaviour.
To reproduce is pretty simple though, simply attempt to call sendBeacon in chrome with a request body larger than 64 kB.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
I found this comment buried in a w3c pull request that references the limitation:
w3c/beacon#39 (comment)
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/sendBeacon
MDN metadata
MDN page report details
api.Navigator.sendBeacon
The text was updated successfully, but these errors were encountered: