There were discussionsa about moving the API from navigator.push to
serviceWorkerRegiatration.push. This would make a lot of sense to me given
that the registration is tied to a service worker rather than a page.
Is this what you are planning to implement? It would be good to avoid
shipping more t
On 2014-07-21, 4:25 PM, nmara...@mozilla.com wrote:
On Monday, July 21, 2014 11:00:13 AM UTC-7, Ehsan Akhgari wrote:
On 2014-07-21, 12:22 PM, Tyler Smith wrote:
Summary: New Push API to replace the current specification for SimplePush.
Purposes include
1) Switching to Promise, which w
On Monday, July 21, 2014 11:00:13 AM UTC-7, Ehsan Akhgari wrote:
> On 2014-07-21, 12:22 PM, Tyler Smith wrote:
>
> > Summary: New Push API to replace the current specification for SimplePush.
>
> > Purposes include
>
> > 1) Switching to Promise, which was sorely needed.
>
> > 2) Establishing
On 2014-07-21, 12:22 PM, Tyler Smith wrote:
Summary: New Push API to replace the current specification for SimplePush.
Purposes include
1) Switching to Promise, which was sorely needed.
2) Establishing that the data field of messages is required.
3) Establishing that all background communicatio
The latest version of the API spec is here:
https://w3c.github.io/push-api/index.html
That’s potentially in flux. What are your plans should something major change?
On 2014-07-21, at 09:22, Tyler Smith wrote:
> Summary: New Push API to replace the current specification for SimplePush.
> Purp
Summary: New Push API to replace the current specification for SimplePush.
Purposes include
1) Switching to Promise, which was sorely needed.
2) Establishing that the data field of messages is required.
3) Establishing that all background communication happens over HTTPS
4) Agreeing that the DOM A
6 matches
Mail list logo
