1867821 - Implement automatic fallback from `sendBeacon` to `fetch` in glean.js

Status: RESOLVED FIXED

(Data Platform and Tools :: Glean: SDK, task, P1)

Description

[Alessio Placitelli [:Dexter]]

We now have a sendBeacon uploader for glean.js. However, on some browsers, sendBeacon might not be available. We need to tweak the provider to fall back to fetch if needed or create a new uploader to experiment with that.

After this is done, we can turn this on by default in glean.js while still offering users a way to switch back to the fetch one.

Comment 1

[Bruno Rosa [:brosa]]

For additional context:

This was implemented this way so that we could test things without breaking the original implementation. We want to always use sendBeacon unless the client explicitly chooses to use fetch. This should be something that is able to be set in the initialize config object.

Our docs should also reflect that by default everyone should be using sendBeacon unless they have a specific reason not to. The reason for sendBeacon was to fix data loss issues caused by page unloads with fetch in Firefox.

Feel free to reach out with any questions about the implementation itself, happy to help.

Comment 2

[Jan-Erik Rediger [:janerik]]

I'll take this.

Comment 3

[BMO Github Automation]

Attachment: [mozilla/glean.js] Bug 1867821 - Implement an uploader that defaults to sendBeacon and falls back to… (#1866)

Comment 4

[Jan-Erik Rediger [:janerik]]

rosahbruno merged PR [mozilla/glean.js]: Bug 1867821 - Implement an uploader that defaults to sendBeacon and falls back to… (#1866) in b1404d0.