Document periodic background sync permission requirements - #45392
Open
SCW5370 wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
Content:WebAPI
sideshowbarker
removed their request for review
August 30, 2026 02:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
I documented the periodic-background-sync permission in the Permissions API list, added security considerations to the Web Periodic Background Synchronization API overview, and linked the register() method to that guidance.
Motivation
I found that the existing pages documented the NotAllowedError but did not explain how to query the permission or the Chrome-specific installation and engagement requirements. This left readers without the context needed to understand why registration may be unavailable or events may not fire.
Additional details
I based the Chrome-specific guidance on the Chrome for Developers article linked from the existing MDN pages and issue discussion.
I validated the three edited pages with:
Related issues and pull requests
Relates to #33692
Relates to #45230