Open Bug 1378096 Opened 6 years ago Updated 1 year ago

Push API in Extensions


(WebExtensions :: General, enhancement, P3)



(Not tracked)


(Reporter: joaomgcd, Unassigned)


(Depends on 1 open bug)


(Whiteboard: [design-decision-needed] triaged investigate [wecg])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.50 Safari/537.36

Steps to reproduce:

Developed an extension and wanted to add support for receiving push messages in it using the Push API.

Actual results:

The Push API needs service workers which aren't supported in Extensions.

Expected results:

I should be able to receive push messages in Extensions.
Component: Untriaged → WebExtensions: General
Product: Firefox → Toolkit
Priority: -- → P3
Whiteboard: [design-decision-needed]
Hi joamgcd, this has been added to the agenda for the July 25 WebExtensions APIs triage. Would you be able to join us? 


Unfortunately I won't be available today at that time, but I'm happy to give some feedback if needed at a different time. Thanks in advance!
Flags: needinfo?(lgreco)
We've discussed about this during the last week WebExtensions APIs triage, and we agreed that the first step is investigating the status of the ServiceWorker in a WebExtensions (e.g. how it should work), if allowing a ServiceWorker from inside a WebExtensions is not feasible, then we will evaluate how to expose the Push API to a WebExtension without the ServiceWorker (e.g. through a new WE API).

Marking this as investigate in the whiteboard (and needinfo assigned to me).
Flags: needinfo?(lgreco)
Whiteboard: [design-decision-needed] → [design-decision-needed] triaged investigate
seems removing ni? was not intentional.
Flags: needinfo?(lgreco)
Severity: normal → enhancement
Product: Toolkit → WebExtensions
Any progress on this issue? It`s really important feature...

Hello Folks,

I'd like to give you an update about this issue. While I can't offer a concrete timeline for support, I do believe there is value in providing push notifications support in WebExtensions. The mechanism to do so would indeed be service workers, I'd like to avoid specific WebExtension APIs that have an equivalent Web API.

There are a few dependencies to making that happen that I don't yet have a bug number for, I will add dependencies when the time comes.

In the meanwhile, I'm restricting comments since this bug has attracted various advocacy comments. I'd like to reserve this bug for technical discussions on making this happen. You are welcome to discuss the merits on if necessary.

Restrict Comments: true

Added Bug 1573659 ([meta] Background Service Worker for Manifest v3) as a blocker for this issue.

Flags: needinfo?(lgreco)
Ever confirmed: true
Whiteboard: [design-decision-needed] triaged investigate → [design-decision-needed] triaged investigate [wecg]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.