988107 - Make sendBeacon work with FirefoxOS apps by setting the correct appId on the request

Status: RESOLVED WONTFIX

(Core :: DOM: Core & HTML, defect)

Description

[(no longer active)]

+++ This bug was initially created as a clone of Bug #987387 +++

This is a spin-off from bug 987387 to cover the case of setting the correct appId on the request.  Josh, what needs to be done here?

Comment 1

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

We'll need to disable sendBeacon for FFOS if we can't get this fixed.

Comment 2

[Josh Matthews [:jdm]]

I am unaware of a way to set an appId without providing a notificationChannelCallbacks or loadGroup that links to nsILoadContext. Maybe we need to create a synthesized one here and link it to the existing notificationChannelCallbacks?

Comment 3

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Ah, yes, the way to do this is probably to create a fresh nsILoadGroup which links to a fresh non-docshell nsILoadContext. Then supply the correct information on that nsILoadContext.

Comment 4

[(no longer active)]

(In reply to Jonas Sicking (:sicking) from comment #1)
> We'll need to disable sendBeacon for FFOS if we can't get this fixed.

FWIW it seems like sendBeacon is disabled everywhere for now.  It's hidden behind the beacon.enabled pref.

Comment 5

[Jason Smith [:jsmith]]

(In reply to Jonas Sicking (:sicking) from comment #1)
> We'll need to disable sendBeacon for FFOS if we can't get this fixed.

Why is this needed specifically for 1.4?

Comment 6

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

It's not. But at the time I thought that the feature was enabled, but in a broken state, for v1.4. Not worth blocking on given that it's already disabled.

Comment 7

[Lukas Blakk [:lsblakk] use ?needinfo]

Given comment 4 and having sendBeacon disabled everywhere, there's no reason to continue tracking this.

Comment 8

[Doug Turner (:dougt)]

> FWIW it seems like sendBeacon is disabled everywhere for now.  It's hidden behind the beacon.enabled pref.

This is no longer true, is it?

Comment 9

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

It is still true for FirefoxOS sadly.