w3c/push-api Issues

Last updated Dec 22, 2024, 5:55:50 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

12 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time past SLO
#289	Make it clear that a push message does not require a payload	❌	6.9 years	6.9 years
#353	Question: what about shared device	❌	2.5 years	2.4 years
#357	New push subscription MUST have an endpoint that's different from the original	❌	2.1 years	2 years
#361	Permission Revocation - English language clarification	❌	1.2 years	1.2 years
#373	PushSubscription and underlying concept should be better separated	❌	5.5 months	5.3 months
#375	oldSubscription is never null	❌	5.5 months	5.3 months
#376	Security and privacy considerations should not contain requirements	❌	5.5 months	5.3 months
#377	PushSubscription IDL links broken	❌	5.5 months	5.3 months
#380	PushMessageData is poorly defined and seems broken	❌	5.5 months	5.2 months
#389	Holding "Fire a Functional Event" incorrectly	❌	3.9 months	3.6 months
#390	Normative references to discontinued specs in Push API	❌	3.8 months	3.6 months
#392	"a service worker registration has at most one push subscription" seems wrong	❌	1.3 months	1.1 months