Skip to content
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

update Notifications API content to better explain persistent events and not persistent events #30931

Open
skyclouds2001 opened this issue Dec 11, 2023 · 0 comments
Labels
accepting PR Feel free to open a PR to resolve this issue Content:WebAPI Web API docs effort: large This task is large effort. goal: clarity (Experimental label) Issues about unclear/confusing/inconcise content.

Comments

@skyclouds2001
Copy link
Contributor

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API

What specific section or headline is this issue about?

No response

What information was incorrect, unhelpful, or incomplete?

see #30717 (review)
reference to https://notifications.spec.whatwg.org/

Our documentation for the Notifications API has a big flaw: we don't explain the difference between persistent events and not persistent events.

This may be done in a follow-up PR, and we would need to update:

  • the overview page (Notifications API) to explain these two concepts.
  • Rework _Using the notifications API", maybe dividing it into two guides, one for persistent notifications (associated with service workers, and one for non-persistent notifications.

What did you expect to see?

ditto.

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata

No response

@skyclouds2001 skyclouds2001 added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Dec 11, 2023
@github-actions github-actions bot added the Content:WebAPI Web API docs label Dec 11, 2023
@caugner caugner added the goal: clarity (Experimental label) Issues about unclear/confusing/inconcise content. label Dec 18, 2023
@dipikabh dipikabh added effort: large This task is large effort. accepting PR Feel free to open a PR to resolve this issue and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepting PR Feel free to open a PR to resolve this issue Content:WebAPI Web API docs effort: large This task is large effort. goal: clarity (Experimental label) Issues about unclear/confusing/inconcise content.
Projects
None yet
Development

No branches or pull requests

3 participants