Update on Push API

# Léonie Watson (a month ago)

Peter & Martin,

Could you post a quick update on progress, especially with the V1 issues [1]?

Thanks. Léonie [1] w3c/push-api/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Av1

Contact us to advertise here
# Peter Beverloo (a month ago)

onie,

There are two more issues (209 and 235) that we'd like to address for v1, for which I'll put up a PR on Thusday. Following that we'd like to conclude v1 and request wider review.

Thanks, Peter

# Léonie Watson (a month ago)

On 18/04/2017 18:09, Peter Beverloo wrote:

There are two more issues (209 and 235) that we'd like to address for v1, for which I'll put up a PR on Thusday. Following that we'd like to conclude v1 and request wider review.

Thanks Peter, that sounds good. When the PR lands I'll get the WD updated and send it out for wide review.

What's the status of tests and/or interop for each feature?

Léonie

# Peter Beverloo (a month ago)

Thank you Léonie, I will send an update when it's been settled.

Creating a comprehensive test suite will be tricky because a lot of the API's functionality is dependent on behaviour provided by the user agent and the push service. I have filed an issue against WPT so that we can at least track this.

w3c/web-platform-tests#5630

If we scope your question down to what's defined in the Push API, and not its dependencies, the core parts of the API have good interoperability between the implementations in Chrome and Firefox. I suppose we'll have to assess this more thoroughly when the specification reaches CR?

Thanks, Peter

# Léonie Watson (17 days ago)

Peter,

When you get a moment could you complete the questionnaire for the security and privacy wide review [1]? Thanks.

Léonie

Want more features?

Request early access to our private beta of readable email premium.