w3c/clipboard-apis Issues

Last updated May 17, 2024, 5:52:23 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.

21 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
#21	List of input types	❌	8.2 years	8.2 years
#39	Add ipr functionality to the spec	❌	7.2 years	7.2 years
#47	WAI-ARIA listbox and custom component support	❌	6.7 years	6.7 years
#48	Clarification for clipboardData.setData() and native access	❌	6.7 years	6.7 years
#60	Request a TAG review for image/delayed-content-generation API	❌	6.4 years	6.3 years
#71	"context is editable" when firing events needs to be defined	❌	6.2 years	6.2 years
#87	write() method incorrect	❌	5.2 years	5.2 years
#106	Restrict Clipboard API to top-level origin	❌	4.5 years	4.5 years
#112	Add Internationalization Considerations section	❌	4.2 years	4.2 years
#114	Add accessibility section	❌	4.1 years	4.1 years
#125	Use bikeshed algorithms more better	❌	3.9 years	3.9 years
#128	Specify how to handle unsupported data types in `write()`.	❌	3.9 years	3.9 years
#184	Cross-device Shared clipboard	❌	1.7 years	1.7 years
#186	Why does the Clipboard interface extends EventTarget?	❌	1.6 years	1.6 years
#187	Broken references in Clipboard API and events	❌	1.6 years	1.6 years
#199	Add method `match` (`clipboard.match(regex)`) to check clipboard for pattern matching before reading - as it is done in iOS	❌	6.3 months	6 months
#203	algorithms don't enforce focus requirement	❌	5.2 months	4.9 months
#205	References to permissions	❌	5.1 months	4.9 months
#209	read(formats) ambiguous	❌	4.1 months	3.9 months
#210	RTF is not exposed when using navigator.clipboard.read()	❌	3.9 months	3.7 months
#213	No provision made for multiple clipboards, e.g. on Linux	❌	2.5 weeks	1.5 weeks