Re: [w3c/push-api] Progressing spec to CR (#334)

Thanks Marcos!

> The `userVisible` seems to be always required... maybe it should just assume true and it could go away? [userVisibleOnly should be standardized to match browser behaviour #313](https://github.com/w3c/push-api/issues/313) ... some people argue that they need non-user-visible

It's not unreasonable that we might eventually allow silent push messages in highly privileged environments, but we have no active plans to pursue this. Using `userVisibleOnly` to signal that feels appropriate, but I don't feel strongly.

> Clarify `expirationTime` [Make PushSubscription.expirationTime mandatory #302](https://github.com/w3c/push-api/issues/302)

I agree in principle, quite strongly even, but we're not ready to act on this. This would be incompatible with much of the existing Web Push API usage, and needs a lot more thought.


#303 - I agree that it's probably worth fixing, the idea is sound and fits well into the narrative we've built around these APIs. I'm not aware of any active developer demand however, so happy to defer this to some point after CR too.

#300 - I do believe that Background Sync would be a sensible mechanism for this, as it's significant harder to abuse than retrying the `push` event on error conditions. However, as neither Firefox nor Safari have adopted it, I'm not comfortable pushing for more than a suggestion. The "sorta online" category of error conditions exists everywhere.

#280 - Although most of the base64url decoding implementations just substitute characters (& thus work fine with either input, modulo the trailing equal-signs that the forgiving algorithm seems to accomodate for), there is _a lot_ of tooling out there, across client and server, and no way for us to know what would break. We shouldn't change this.

#292 - We would like this, but evidently haven't properly prioritised it either. OK with deferring to after CR.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/334#issuecomment-951802738