Closed
Bug 1281444
Opened 8 years ago
Closed 6 years ago
navigator.sendBeacon for workers
Categories
(Core :: DOM: Workers, defect, P3)
Tracking
()
RESOLVED
INVALID
People
(Reporter: smaug, Unassigned)
References
Details
(Whiteboard: [tw-dom])
Looks like we don't support sendBeacon in workers. Per https://w3c.github.io/beacon/#sec-sendBeacon-method we should.
|
Reporter | |
Comment 1•8 years ago
|
||
I'm not familiar with sendBeacon implementation, but maybe sicking or ehsan could mentor this one?
It was told that Edge keeps network alive in workers a bit longer than the rest of the worker to give sendBeacon better chance to succeed.
Whiteboard: [tw-dom]
|
||
Updated•8 years ago
|
Whiteboard: [tw-dom] → [tw-dom] btpp-backlog
|
|
||
Updated•8 years ago
|
Priority: -- → P3
Whiteboard: [tw-dom] btpp-backlog → [tw-dom]
|
||
Comment 2•6 years ago
|
||
sendBeacon is not exposed to workers. See the latest spec: https://w3c.github.io/beacon/#sendbeacon-method
Spec says: "partial interface Navigator {.." and Navigator is not exposed to workers. In workers we have WorkerNavigator:
https://html.spec.whatwg.org/multipage/workers.html#workernavigator
"The navigator attribute of the WorkerGlobalScope interface must return an instance of the WorkerNavigator interface, which represents the identity and state of the user agent (the client):"
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•