Best practices to dismiss web push notifications cross devices
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- javascript
- 领域
- api
调研方向
The issue describes synchronizing notification dismissal across devices through the Push API and service workers, but names no repository files or tests. Start by reading the Push API specification sections on subscriptions and push events, then identify whether the API can support the requested behavior. Done would mean documenting or specifying a supported approach that lets a notification read on one device disappear on the others.
由索引模型根据 Issue 内容生成。
描述
Hello,
I'm working on a web application that allows receiving push notifications on different devices. I would like to ensure that when a user reads a notification on one device, it gets removed from the others.
I wanted to use subscribe with userVisibleOnly: false, but it seems that Chrome doesn't currently support it...
It seems that if no notification is sent for a "push" event at the service worker level, the browser may display a warning notification to the user indicating that it's working in the background.
I was thinking of including the IDs of my unread notifications in each push and removing any notifications that don't match before adding the new one. However, I'm still facing an issue if I have only one notification and it becomes read.
What are the current best practices to achieve this?
Have a good day.
Maxime
- 主要语言
- 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
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
zold-io/wts.zold.io#620 ·
维护者通常 1 天内回复
-
bug file-compat priority: medium
难度 2/5 1-3 小时 新手友好度 78/100
storytold/wordcraft#6209 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
-
backlog multiple issues priority: low
难度 2/5 1-3 小时 新手友好度 72/100
storytold/pdfcraft#6911 · 2 条评论 ·
维护者通常 2 天内回复