On 2014-07-21, 4:25 PM, [email protected] 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 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 API should not have to care what Push backend the
device is using
5) Playing nicer with the interface exposure model (earlier we just
wouldn't show navigator.push to apps without permission)
Can you please clarify what you mean here? How are you looking to
expose the new property?
Ah, this is my fault in explaining things a bit wrong to Tyler. It'll be
exposed the way we expose all the other APIs, nothing special. It will be
hidden behind dom.push.enabled, although I'd like it to be enabled by default
on non Release builds. The new spec is exposed as
navigator.pushRegistrationManager so it does not conflict with navigator.push.
That sounds good.
Hmm, the spec here <https://w3c.github.io/push-api/index.html> talks
about navigator.push. Is that something that is going to change in the
spec?
Sadly the spec hasn't been updated in several months. Eduardo, one of the
editor's intends to get on it in August after he is back from vacation.
Understood. No concerns form me there as long as we keep up with the
developments on the spec side as our implementation makes progress.
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
