w3c/compute-pressure Issues

Last updated Nov 21, 2024, 5:52:20 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
#110	Permission policy doesn't support workers yet	❌	2.5 years	2.5 years
#116	Consider adding averages	❌	2.4 years	2.4 years
#119	Use-case: optimize for long battery life	❌	2.2 years	2.2 years
#120	Use-case: Memory stalls	❌	2.2 years	2.2 years
#177	Wide review tracker	❌	1 year	1 year
#243	Permission policy needs to be checked when owner set changes	❌	1 year	1 year
#273	"Valid source type" check in PressureObserver.observe() needs more details	❌	5.7 months	5.5 months
#285	automation: Decide whether shared workers should be supported	❌	5.3 months	5 months
#286	automation: Pressure types supported in WebDriver are the same as what PressureObserver.knownSources returns	❌	5.3 months	5 months
#288	automation: Consider adding WebDriver BiDi actions in addition to the WebDriver Classic endpoints	❌	5.1 months	4.8 months
#290	Usecase: 100% pressure, main thread blocked entirely. PressureObserver never fires an event	❌	4 months	3.8 months
#295	Metabug: Raising Specification to CR maturity level.	❌	1.8 months	1.6 months