Issues: w3c/push-api
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Permission Revocation - English language clarification
editorial
#361
opened Sep 26, 2023 by
karlcow
New push subscription MUST have an endpoint that's different from the original
#357
opened Dec 2, 2022 by
collimarco
Browser MUST always display a permission prompt after a user interaction
#356
opened Aug 5, 2022 by
collimarco
Documentation: It's not clear how to specify the push service
editorial
#355
opened Jul 27, 2022 by
DarkTrick
Mention or enforce userVisibleOnly check in PushManager.subscribe?
bug
editorial
#339
opened Oct 11, 2021 by
youennf
Should there be a UTF-8 health warning?
editorial
i18n-needs-resolution
Issue the Internationalization Group has raised and looks for a response on.
#335
opened Aug 5, 2021 by
aphillips
pushsubscriptionchange event doesn't have oldSubscription in it.
editorial
#325
opened May 5, 2020 by
novaknole
userVisibleOnly should be standardized to match browser behaviour
bug
#313
opened Jul 25, 2019 by
mgiuca
A javascript api for sending push notifications to others
enhancement
#303
opened Nov 30, 2018 by
jimmywarting
Make it clear that a push message does not require a payload
bug
#289
opened Jan 19, 2018 by
collimarco
ProTip!
Exclude everything labeled
bug
with -label:bug.