Allow atomic push resubscribe
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- javascript
- 领域
- api
调研方向
Start by reading the Push API subscription refresh algorithm linked in the issue and the surrounding PushManager specification. Work out how an atomic resubscribe method would interact with pushsubscriptionchange and subscription failure; done would mean the proposed behavior and returned promise are specified clearly. The thread has been inactive for years, so check whether the proposal is still relevant before starting.
由索引模型根据 Issue 内容生成。
描述
I was wondering if we can consider having an atomic resubscribe method for push? Apparently there are sites that unsubscribe and then try to subscribe again and then they lose their subscription if the browser is closed, for instance. It would be ideal if we were able to subscribe another channel and then if it succeeds, we remove the old channel.
After chatting with @beverloo, it sounded like we should have something like PushManager.refreshSubscription() that invokes the refresh algorithm and would return a Promise<void> that'd be resolved when the pushsubscriptionchange event has finished executing.
- 主要语言
- HTML
- 星标
- 158
- 派生
- 43
- 平均合并
- 2 天 6 小时
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
w3c/push-api 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 4/5 3-5 天 新手友好度 30/100
-
Do we want to allow a subscription from window.pushManager to fire push event for non-DWP messages?未关闭
难度 5/5 一周以上 新手友好度 18/100
-
难度 5/5 一周以上 新手友好度 12/100
相似的 Issue
-
module/data.yaml Type/Bug
难度 2/5 1-3 小时 新手友好度 73/100
ballerina-platform/ballerina-library#9667 ·
维护者通常 1 天内回复
-
security
难度 2/5 1-3 小时 新手友好度 64/100
IBM/ibmi-mcp-server#256 ·
维护者通常 7 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
zilliztech/milvus-backup#1386 ·
维护者通常 1 天内回复
-
Pipelined flush no longer observes kill signals after #2042: flush backoffer is built with nil vars未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
zilliztech/memsearch#853 ·
维护者通常 1 天内回复