mdn / mdn/browser-compat-data

api.SyncManager - Background Synchronization APIs should be marked non-standard

Open
#28,155 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

data:api
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

MDN URL

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

What specific section or headline is this issue about?

All

What information was incorrect, unhelpful, or incomplete?

I've recently created PWAscore, and I've gotten very strong feedback that SyncManager and other Background Synchronization APIs should be marked as "Experimental".

What did you expect to see?

I'd expect that SyncManager and other Background Synchronization APIs should be marked as "Experimental" both on the site and in the supporting data.

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

As evidence, https://wicg.github.io/background-sync/spec/ is watermarked "UNOFFICIAL DRAFT" and explicitly states, "It is not a W3C Standard nor is it on the W3C Standards Track". Mozilla (https://mozilla.github.io/standards-positions/#background-sync) and Apple (https://github.com/WebKit/standards-positions/issues/14) have also expressed concerns, and (AFAIK) neither has committed to support it.

Do you have anything more you want to share?

No response

MDN metadata
Page report details

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the SyncManager entry referenced in the issue and review the linked Background Sync specification and standards-position references. Check how the API’s status is represented in the supporting compatibility data and verify the MDN page at en-us/web/api/syncmanager; done means the requested status is consistently reflected in both places.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.