Firing `pushsubscriptionchange` when permission is regranted

未关闭
#236 5 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

@antosart 已经在做这个了。

开始于 2025年4月22日。

  • #400 来自 @antosart —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
html
领域
api

调研方向

Read the Push API specification language covering pushsubscriptionchange and permission changes, then review the linked pull request #400 for the proposed wording. The issue asks whether existing language can cover reinstating suspended subscriptions when notification permission returns; done means the specification accommodates that use case without prescribing specific circumstances.

由索引模型根据 Issue 内容生成。

描述

v2

Firefox currently fires pushsubscriptionchange when an origin gets permission regranted.

We are considering doing the same in a slightly different scenario; some operating systems enable users to disable entire applications (i.e. the browser) from showing notifications. Since we still tie push to notifications, it may not make sense to continue receiving messages in this scenario. When the user allows the application to show notifications again, suspended subscriptions should be able to be reinstated.

I don't think it's a good idea to specify the specific circumstances under which this can happen. Rather, we need to make sure that the language we have allows for these use-cases.

/cc @kitcambridge

主要语言
HTML
星标
158
派生
43
平均合并
2 天 6 小时
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

w3c/push-api 的其他 Issue

查看 w3c/push-api 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。