A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members) or send an e-mail to admin@wiki.whatwg.org with your desired username and an explanation of the first edit you'd like to make. (Do not use this e-mail address for any other inquiries, as they will be ignored or politely declined.)

Note: This wiki is used to supplement, not replace, specification discussions. If you would like to request changes to existing specifications, please use IRC or a mailing list first.

New Features Awaiting Implementation Interest

From WHATWG Wiki
Jump to: navigation, search

There are features that have been requested, but for which we are lacking implementor interest. Without two or more vendors interested in implementing the feature, they are unlikely to get added to the specs.

Feature Interest indicated by... Comments
Mozilla (Firefox) Opera Microsoft (IE) Apple (Safari) Google (Chrome) Others
Some way to add files to <input type=file> Jonas Sicking Nico Weber On track for spec
Cross-origin seamless iframes Boris Zbarsky Adam Barth Pending input on this thread
HTMLCanvasElement.printCallback API Julian Viereck
Metadata API for media elements Ralph Giles Also needs a spec for the metadata schema
Adding defer/async to inline scripts Jonas Sicking
<meta name="referrer"> Adam Barth
Location.ancestorOrigins Already implemented Negative feedback from Tobie Langel
A method to trigger autofill Elliott Sprehn, Peter Kasting
Prerendering APIs Gavin Peters Needs detailed specification work to describe what happens with scripts running in the prerender context (since normally scripts can't run in non-active documents, and normally there's only one active document per session history).
APIs for 'palpable' content (at the bottom) Ojan Vofai
Appcache: More detail in error events Michael Nordman
Making drawImage() have a mode to clamp at source rectangle Justin Novosad There is a workaround using ImageBitmaps to extract a subregions of the source image. The workaround does not solve cases where sub-region extraction needs to be synchronous either because the source image content changes over time (e.g a canvas or video), or because the subrectangle coordinates cannot be determined in advance.
Appcache: Interceptor Worker Needs use cases as well
FormData
Canvas: Stroke alignment
Canvas: Page flipping for the 2D context James Robinson
Canvas: control over when shadows paint
<img srcset>: a mechanism to enable adaptive images Implemented
locale=""
<video> currentTime and seek using rational numbers Jer Noble Would expose the video's timebase, too, assuming it's constant. See also next line.
video source material metrics (e.g. frame rate for fixed-frame-rate video data)
Cross-origin workers Travis Leithead? Ojan Vafai
Deferring <img> loads until the image is needed
API to request Web Worker latency guarantees (in exchange for guaranteeing low CPU usage)
SearchBox API Tony Gentilcore No longer being tracked.

See also: Who to ask about stuff