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

Difference between revisions of "Specs/todo"

From WHATWG Wiki
Jump to: navigation, search
(MISC: Add some informational links about GIFs.)
Line 47: Line 47:
 
* JS changes: [[Web ECMAScript]]
 
* JS changes: [[Web ECMAScript]]
 
* Animated GIFs need a spec that, in particular, specifies how to handle timings (not all browsers honour all values, so we should specify what needs to be honoured exactly)
 
* Animated GIFs need a spec that, in particular, specifies how to handle timings (not all browsers honour all values, so we should specify what needs to be honoured exactly)
 +
** GIF87a: [http://web.archive.org/web/20100929230301/http://www.etsimo.uniovi.es/gifanim/gif87a.txt Text]
 +
** GIF89a: [http://www.w3.org/Graphics/GIF/spec-gif89a.txt Text] / [http://odur.let.rug.nl/~kleiweg/gif/GIF89a.html HTML]
 +
** [http://www.matthewflickinger.com/lab/whatsinagif/ What's in a GIF]
 +
** [http://odur.let.rug.nl/~kleiweg/gif/netscape.html GIF Application Extension: NETSCAPE2.0]
 +
** [http://www.theimage.com/animation/toc/toc.html Gifology: Understanding GIF Files & GIF Animation]
 +
** [http://web.archive.org/web/20100929231133/http://www.etsimo.uniovi.es/gifanim/gifabout.htm All About GIF89a]
 
* Client-side HTTP implementation requirements specification ("option 3" in http://www.w3.org/mid/20101101063413.bf1d8102.eric@bisonsystems.net)
 
* Client-side HTTP implementation requirements specification ("option 3" in http://www.w3.org/mid/20101101063413.bf1d8102.eric@bisonsystems.net)
 
* innerText and outerText, if browsers don't remove them entirely
 
* innerText and outerText, if browsers don't remove them entirely

Revision as of 21:59, 12 October 2012

There are many specifications that need editors. This page lists some of the more important ones. If you want to volunteer to edit one of these specs, contact ian@hixie.ch, post on the WHATWG mailing list or say something on IRC.

See also: Specs with editors, Howto spec.

Platform

  • A specification that defines how XML maps to DOM Core. (I think this should be in DOM Parsing and Serialization. Well really in XML.)
  • X-Frames-Options
  • multipart/form-data
  • HTTP (error handling in particular)
  • APNG (other image formats too maybe?)

APIs

CSS

There are many specifications for extending CSS that are in need of editors. The most important ones are:

Registries

Currently, the state of registries on the Web (and indeed for the Internet in general) is a disaster. At a minimum, the following registries need dramatically updating:

  • MIME types
  • Schemes

It's possible that the right solution is to change approach altogether (e.g. moving more to a wiki model of registries).

See also: Registries

MISC

Other stuff

http://lists.w3.org/Archives/Public/public-html/2008Oct/0127.html has a description of some sections that needed editing in 2008 and how much work they would be.

Some notes from the HTML5 spec about things that need doing: