my...@chromium.org, fer...@chromium.org, deno...@chromium.org
https://github.com/darrenw/docs/blob/main/explainers/beacon_api.md
https://clelland.github.io/page-unload-beacon/spec.html (In draft state)
A stateful API for beacons that has the browser control the time beacons are sent.
Existing beacon APIs are all based around a developer constructing and sending a beacon, and there's no good time for that "send" call to be made. (Handlers such as 'unload' are often ignored, for example.) This API delegates the sending to the browser itself, so it can support beacons on page unload or on page hide, without the developer having to implement send calls at exactly the right times.
None yet.
N/A
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
The intent is for experiments to learn that developers can easily adopt the API shapes to achieve current use cases in addition to getting feedback from them. The experiment also aims to test the stability and reliability of the API.
In M104, the API described in the explainer is not yet fully developed, such that the API
Supports only the GET method. Setting it to POST will fall back to GET.
Does not support request payload, i.e. it does not send out data set by setData(data).
Does not support pageHideTimeout.
Does not recover from browser crashes, forced closures, network failure, etc.
There are no particular debugging APIs made available or Chrome DevTools integrations for this OT. We plan to build an integration with Chrome DevTools to provide a better developer experience. This OT will allow us to get feedback that helps us build the right design.
Yes
No, basic tests are present and we will be adding more as we complete more of the implementation.
PendingBeaconAPI
False
https://bugs.chromium.org/p/chromium/issues/detail?id=1293679
https://bugs.chromium.org/p/chromium/issues/detail?id=1323615
M104 for off-by-default experiment
https://chromestatus.com/feature/5690553554436096
Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAG%2BRaU7yMQ%2BRkeSpXhgbfCSGb4BvpW-exTUFZzb_eMFRE%2B_syQ%40mail.gmail.com
Contact emails
my...@chromium.org, fer...@chromium.org, deno...@chromium.org
Explainer
https://github.com/darrenw/docs/blob/main/explainers/beacon_api.md
Specification
https://clelland.github.io/page-unload-beacon/spec.html (In draft state)
Summary
A stateful API for beacons that has the browser control the time beacons are sent.
Existing beacon APIs are all based around a developer constructing and sending a beacon, and there's no good time for that "send" call to be made. (Handlers such as 'unload' are often ignored, for example.) This API delegates the sending to the browser itself, so it can support beacons on page unload or on page hide, without the developer having to implement send calls at exactly the right times.
Blink component
TAG review
None yet.
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5690553554436096
Links to previous Intent discussions
Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAG%2BRaU7yMQ%2BRkeSpXhgbfCSGb4BvpW-exTUFZzb_eMFRE%2B_syQ%40mail.gmail.com
This intent message was generated by Chrome Platform Status.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAH3JASV7pR%3D3poOA0x2sQgVLOobtjCyfxLE3kYsnasfBVSyOEg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAozHLnkGKfSNuhgdT9yMUVFVe-S2s%3D%2B9mLAg6uJE9O2tLHuUg%40mail.gmail.com.
https://github.com/WICG/unload-beacon/blob/main/README.md
https://wicg.github.io/unload-beacon/ (In draft state)
Hi all,Reviving this thread as we plan to conduct an Origin Trial for this feature in M106, with the following updates. Please take a look.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAH3JASU9Q8aJMnHhWBNtos_nLQEsUxebVDM--OUGaThE8DRyuQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B_JMTzX5mni0CAqxKRaWNOecRB9N_PtHBmejbYiG1_1Ocy2fg%40mail.gmail.com.
Hi Ian & Yoav,We might have to delay the OT to M107-M109 as we still have several issues to solve. Could it be updated?