For a consumer like the Background Task Runtime's individual background tasks, we need a JS-accessible FOG init function that can take a custom application id. Otherwise if and when it sends builtin pings they'll look as though they've come from Firefox Desktop itself.

This work could've been done in bug 1694505 but I scoped that bug too narrowly.

Note that, should a background task choose to use its own application id (which it should), it will need to file the appropriate bug to have itself added as a new application_id, and it should consider listing itself under Firefox Desktop's app_name so it appears as a "variant" in the same family.

(In reply to Chris H-C :chutten from comment #0)

Note that, should a background task choose to use its own application id (which it should), it will need to file the appropriate bug to have itself added as a new application_id, and it should consider listing itself under Firefox Desktop's app_name so it appears as a "variant" in the same family.

It's going to be another "channel" of Firefox Desktop then (because that's how we differentiate multiple variants under a single app name).
I think that's still fine though

Backed out for causing build bustages

Backout link: https://hg.mozilla.org/integration/autoland/rev/9df021167d90c072d0be81f66b2793d68e6646b0

Push with failures

Failure log

Well that's embarrassing.

This time I triple-checked that I linted, built, ran, and passed tests.

https://hg.mozilla.org/mozilla-central/rev/d17549cef399