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


From WHATWG Wiki
< Specs
Revision as of 07:42, 30 September 2009 by Annevk (talk | contribs) (remove items covered by CSSOM View (which unlike CSSOM still has a somewhat active editor))
Jump to: navigation, search

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, contain ian@hixie.ch or post on the WHATWG mailing list or say something on the #whatwg IRC channel on Freenode.

How to edit a spec

We have some documentation on how to write a spec that could help if you want to help out.

Specs to edit


  • A rewrite of DOM2 Traversal.
  • A rewrite of DOM2 Range.
  • User Interaction Events (onclick, onkeypress, etc).
    • e.g. need to define somewhere that if you cancel mousedown, an element can't get focus
  • window.atob
  • window.btoa
  • XMLSerializer()
  • DOMParser()


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

  • CSS3 Flexible Box or some other UI layout model
  • CSS Animation
  • CSS Gradients

See also

Other stuff

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

  • support access Array element via () instead of [] (IEism) https://bugzilla.mozilla.org/show_bug.cgi?id=289876
  • Need to say that NodeList's items are enumerable, so that... for (var x in myNodeList) { } ...works. (ack Dethe Elza)
  • a way to show icons for file types e.g. http://www.gadgetopia.com/2004/05/04/FileIconTag.html (this should probably be a function for the 'content', 'background-image' and 'list-style-image' properties in CSS)
  • custom syntax highlighting in <textarea>, <pre> (ack Ryan Johnson) (this would probably best be done as some sort of output filter at the CSS level, rather than anything HTML-specific. It would have to support both <textarea>, where the data isn't in the DOM proper, and <pre>, where it is.)