[whatwg] Feature requests that I've converted to bugs II
Over the years I've collected a number of threads on this list that were requesting features (as opposed to reporting bugs), and which lacked immediate interest from more than one browser vendor. I collected a bunch of them and filed bugs for them back in July: http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Jul/0193.html I've now done the same with a few more threads of feedback sent to this list that I've looked at since then. Here are the bugs I filed (or found already existed) this time around: Mechanism for allowing cloud storage providers to hook into type=file https://www.w3.org/Bugs/Public/show_bug.cgi?id=23497 Make .files writable https://www.w3.org/Bugs/Public/show_bug.cgi?id=22682 media.srcObject = aBlob, img.srcObject = aBlob https://www.w3.org/Bugs/Public/show_bug.cgi?id=23502 : a mechanism by which pages can indicate if their audio should play in the background https://www.w3.org/Bugs/Public/show_bug.cgi?id=23505 : Forced subtitles https://www.w3.org/Bugs/Public/show_bug.cgi?id=23507 Linking to a page with a fragment identifier that causes a particular media element to be shown and to seek to a particular position https://www.w3.org/Bugs/Public/show_bug.cgi?id=23492 : preciseSeek() https://www.w3.org/Bugs/Public/show_bug.cgi?id=23493 Depends on: currentTime in frames rather than seconds https://www.w3.org/Bugs/Public/show_bug.cgi?id=8278 expose the frame rate and specific frames of the media resource https://www.w3.org/Bugs/Public/show_bug.cgi?id=22678 Have a way to define low-priority style sheets (e.g. for printing) https://www.w3.org/Bugs/Public/show_bug.cgi?id=23506 Media-specific scripts (
[whatwg] Feature requests that I've converted to bugs
Over the years I've collected a number of threads on this list that were requesting features (as opposed to reporting bugs), and which lacked immediate interest from more than one browser vendor. Unfortunately, while I've been tracking them, they don't have much visibility and so I don't always know if a particular topic has grown more interest from implementors, since vendors don't know to tell me. To address these problems, I've gone through the feature request threads, and extracted from them all the use cases and constraints I could find, and then using that filed bugs for each feature request. Here are the bugs I filed (and some earlier ones that covered the same topics, for completeness): Aligning strokes inside or outside a path https://www.w3.org/Bugs/Public/show_bug.cgi?id=22674 Features to control the "Referer" header https://www.w3.org/Bugs/Public/show_bug.cgi?id=22675 APIs for page prerendering https://www.w3.org/Bugs/Public/show_bug.cgi?id=22676 expose the frame rate and specific frames of media resources https://www.w3.org/Bugs/Public/show_bug.cgi?id=22678 Localisation https://www.w3.org/Bugs/Public/show_bug.cgi?id=21289 https://www.w3.org/Bugs/Public/show_bug.cgi?id=17859 https://www.w3.org/Bugs/Public/show_bug.cgi?id=22679 Make FormData expose its contents https://www.w3.org/Bugs/Public/show_bug.cgi?id=22680 Make .files writable https://www.w3.org/Bugs/Public/show_bug.cgi?id=22682 Web Intents https://www.w3.org/Bugs/Public/show_bug.cgi?id=22683 Inline
