1188675 - Add some devtools for push notifications

Status: NEW

(DevTools :: Application Panel, enhancement, P3)

Description

[(no longer active)]

If a developer wants to debug push messages, triggering them from the server side may be problematic since they may run out of their push message quota.

It seems like at the minimum, our devtools needs to make it possible to simulate receipt of push notifications.

Comment 1

[Martin Thomson [:mt:]]

Sounds like a good idea; though I'll note that as long as you are visiting the site, you don't need to worry about the quota.

Comment 2

[Jeff Griffiths (:canuckistani) (:⚡︎)]

Cc'ing / needinfo'ing Axel so he's got this on his radar.

Comment 3

[Axel Kratel]

It's going be be nearly impossible to artificially simulate a push notification: as per the W3C standard, "The push API enables delivery of arbitrary application data to webapps, and makes no assumptions about the over-the-air/wire protocol used by push services. As such, the details of what types of data flow through a push services for a particular webapp are specific to the push service and webapp. As needed, clarification about what data flows over-the-air/wire should be sought from push service operators or webapp developers."


I propose we breakdown the features into three buckets:

1) Push notification worker discovery: as a developer I would like to get a list of the the registered workers. 
- service worker, domain, and expected data format, token and channel ID. 

2) Navigate from registered worker to code: as a developer I'd like to be able to easily be able to find the code associated with a given registered worker and set a break point so I can debug on receipt of the notification. 

3) Simulation of push notification: 
Provide an easy syntax for accessing a registered worker via the console as opposed to having to message to it via the server. Will follow up to see if there's already a way to do this from within the browser.

Comment 4

[Martin Thomson [:mt:]]

It should be relatively trivial to induce the creation of a "push message".  We might need to build some hooks into the push module to support that, but I think that it would be valuable.  The input you want to take for this is a BufferSource (ArrayBuffer, etc...).

Alternatively, if you had a generic capability to synthesize events for service workers, then making a synthetic push message is trivial.

Comment 5

[blewett223]

https://www.mykfcexperience.online/

Comment 6

[James Alex]

It ought to be moderately minor to initiate the formation of a "push message". We may have to incorporate a few guides into the push module to help that, however I imagine that it would be significant. The information you need to take for this is a BufferSource (ArrayBuffer, etc...). https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox

On the other hand, assuming you had a nonexclusive capacity to orchestrate occasions for administration laborers, making an engineered push message is paltry. https://bodysolutionskc.com/