w3c/webappsec-permissions-policy Issues

Last updated Nov 21, 2024, 5:57:34 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.

20 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
#77	Using FP to support safe pre-rendering	❌	7.5 years	7.5 years
#90	Clarify child inheritance	❌	7.1 years	7.1 years
#132	Feature Proposal: cross-origin rootBounds and rootMargin	❌	6.8 years	6.8 years
#169	Policies based on device criteria	❌	6.5 years	6.5 years
#198	Clipboard Access	❌	6.3 years	6.3 years
#242	Very Hard to Read If Dark Theme is used with the dev tools	❌	6 years	6 years
#264	Feature Policy to Enforce/Avoid Feature Policy Propagation to Auxiliary Contexts	❌	5.9 years	5.9 years
#277	Terminology issues relating to "feature" and "disabled"	❌	5.8 years	5.7 years
#320	Feature idea: non-strict-mode	❌	5.5 years	5.4 years
#358	Fix navigation race	❌	5 years	4.9 years
#390	Update "creating a feature policy" to use embedder	❌	4.4 years	4.4 years
#419	Replace references to the "sync-xhr" policy-controlled feature	❌	3.7 years	3.6 years
#426	Provide example permission policy control via JS Element.setAttribute()	❌	3.5 years	3.5 years
#435	explain 'none' more fully	❌	3.1 years	3.1 years
#490	Update web-platform-tests	❌	2 years	2 years
#499	Update "Is feature enabled in document for origin?" behavior	❌	1.9 years	1.9 years
#510	Clarify the expected usage of "Should request be allowed to use feature?"	❌	1.7 years	1.6 years
#527	Inconsistency in text and parsing algorithm (invalid member value)	❌	1.4 years	1.4 years
#550	Example 3 is misleading/Delegating Trust to Nested Contexts	❌	5.1 months	4.9 months
#555	Default Powerful Feature Permission	❌	3 months	2.7 months