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

Hi @martinthomson, @beverloo, I've done some triage... this is what I found:

CR blockers: 

 * Firefox doesn't yet support the subscription events and some other things are out of date. E.g., https://github.com/w3c/push-api/issues/325 (there is a bunch of other stuff, mostly FF internal)
 * The `userVisible` seems to be always required... maybe it should just assume true and it could go away? https://github.com/w3c/push-api/issues/313 ... some people argue that they need non-user-visible
 * Clarify `expirationTime` https://github.com/w3c/push-api/issues/302
 * add "utf-8 health warning" https://github.com/w3c/push-api/issues/335
 * Handle permission change https://github.com/w3c/push-api/issues/236
 * Bug: clarify what to do when there is no payload. https://github.com/w3c/push-api/issues/289

I'm unsure what to do with these 4 though:

 * https://github.com/w3c/push-api/issues/303
 * https://github.com/w3c/push-api/issues/300
 * https://github.com/w3c/push-api/issues/280
 * https://github.com/w3c/push-api/issues/292

Could use some guidance. 

-- 
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-948288062