w3c/FileAPI Issues

Last updated Dec 22, 2024, 5:51:19 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.

17 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
#12	IANA Considerations	❌	9.4 years	9.4 years
#45	Re-word the way the various read operations are defined	❌	8.4 years	8.4 years
#66	Set FileReader.error to an AbortError when abort() is called.	❌	7.9 years	7.9 years
#71	Describe internal slots of Blob and File objects better	❌	7.8 years	7.8 years
#95	Consider adding the hashed filesystem path	❌	6.9 years	6.9 years
#120	Event handler content attributes are for HTML elements, not JS APIs	❌	5.8 years	5.8 years
#121	Use [NewObject] for Blob's slice() and FileReaderSync	❌	5.8 years	5.8 years
#124	"package data" reuses type variable	❌	5.7 years	5.7 years
#133	Refactor text() et al to share more infrastructure with Fetch	❌	5.5 years	5.5 years
#135	Sort out when blob: URLs can be fetched / navigated	❌	5.4 years	5.4 years
#146	Add Internationalization Considerations section	❌	4.8 years	4.8 years
#152	Add accessibility section	❌	4.7 years	4.7 years
#174	Consider allowing re-reads after snapshot state change for applications loaded from file: URIs	❌	3.5 years	3.5 years
#185	Broken references in File API	❌	2 years	2 years
#187	Function signature change: reading all bytes from a stream	❌	2 years	2 years
#194	Specify actual byte reading algorithm for Blob.stream()	❌	1.6 years	1.6 years
#199	Meta - make reading algorithms more explicit	❌	2.9 months	2.7 months