[whatwg] Feature requests that I've converted to bugs

Ian Hickson ian at hixie.ch
Tue Jul 16 13:21:25 PDT 2013


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):

   <canvas> 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

   <video> 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 <input type=file>.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 <script async>
   https://www.w3.org/Bugs/Public/show_bug.cgi?id=22696

   An API to detect palpable content, so you can tell in an editor if
   a paragraph is empty
   https://www.w3.org/Bugs/Public/show_bug.cgi?id=22697

   API to make <canvas> prettier when printing
   https://www.w3.org/Bugs/Public/show_bug.cgi?id=22698

   Expose the origins of ancestor frames
   https://www.w3.org/Bugs/Public/show_bug.cgi?id=22699

   Inline Web worker scripts
   https://www.w3.org/Bugs/Public/show_bug.cgi?id=22700

   Full form autofill triggered by page request
   https://www.w3.org/Bugs/Public/show_bug.cgi?id=22701

   appcache: More detailed error information
   https://www.w3.org/Bugs/Public/show_bug.cgi?id=22702

   <canvas> Masks
   https://www.w3.org/Bugs/Public/show_bug.cgi?id=22703

   <canvas> Layers
   https://www.w3.org/Bugs/Public/show_bug.cgi?id=22704

I have also been keeping track of feature requests and which browser
vendors are interested in implementing which features on the wiki:

   http://wiki.whatwg.org/wiki/New_Features_Awaiting_Implementation_Interest

I urge implementors who are interested in implementing any of these
features to say so in the bugs or on the wiki page, so that I know
which features are ripe for speccing, and which would just get ignored.

(If you are bcc'ed to this e-mail, you probably contributed to a thread 
that resulted in one of the bugs above being filed. A few people may have 
been bcc'ed who did not contribute to these threads. Please accept my 
apologies for any inconvenience caused.)

Cheers,
-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'



More information about the whatwg mailing list