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 Chat (such as one of these permanent autoconfirmed members).

Specs/todo: Difference between revisions

From WHATWG Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
HTML5 doesn't stand alone, it's just one of many specifications that form part of the Web platform. Many of these are currently orphaned or neglected; if you want to help, you could try editing one! We have [[HowToWriteASpec|some documentation on how to write a spec]] that could help.
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 [email protected] or post on the WHATWG mailing list or say something on the #whatwg IRC channel on Freenode.


* CSS3 - there's a [http://www.w3.org/Style/CSS/current-work whole slew] of specifications for extending CSS that are in need of editors. In particular:
== How to edit a spec ==
** the CSS3 Flexible Box module
** animation
** gradients
* updates to DOM2 Traversal and DOM2 Range.
* CSSOM - the specification for scripted manipulation of style, both the existing interfaces and new interfaces to make it easier. (Parts are being done by Anne at the moment.)


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


These sections of HTML5 could easily be taken out and make into independent specs:
== Specs to edit ==
* 2d context for canvas (this is pretty stable right now, so it would probably be a bad time to work on it)
* 3d context for canvas


=== DOM ===


These specs currently have active editors, but have historically spent time abandoned:
* A rewrite of DOM2 Traversal.
* DOM3 Events
* A rewrite of DOM2 Range.
* Keyboard Events -- .charCode, .keyCode, and related stuff (mostly defining legacy interfaces)
* User Interaction Events (onclick, onkeypress, etc).
* setTimeout
* [http://developer.mozilla.org/En/DOM/Window.atob window.atob]
* Web DOM4 Core -- culling the server-side features from DOM3 Core, adding features that would help the web, adding generic exceptions that would help other specs out.
* [http://developer.mozilla.org/En/DOM/Window.btoa window.btoa]


=== CSS ===


See also:
There are [http://www.w3.org/Style/CSS/current-work many specifications for extending CSS] that are in need of editors. The most important ones are:
* http://lists.w3.org/Archives/Public/public-html/2008Oct/0127.html which lists (ordered here by total time estimated):
* CSS3 Flexible Box or some other UI layout model
** altss - 300h over 2y
* CSS Animation
** url - 300h over 2y to 1260h over 3y
* CSS Gradients
** common dom - 620h over 3y
* [[http://dev.w3.org/csswg/cssom/|CSSOM]]
** sniffing - 890h over 3y
 
** undo - 940h over 4y
== See also ==
** events - 1050h over 4y
 
** 2d - 1230h over 4y
* http://lists.w3.org/Archives/Public/public-html/2008Oct/0127.html (a description of some sections that needed editing in 2008 and how much work they would be)
** 3d - 1570h over 4y
** rendering - 2740h over 4y
** window - 5300h over 4y
* [[Needs specification]]

Revision as of 07:24, 3 July 2009

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 [email protected] 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

DOM

  • A rewrite of DOM2 Traversal.
  • A rewrite of DOM2 Range.
  • User Interaction Events (onclick, onkeypress, etc).
  • window.atob
  • window.btoa

CSS

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
  • [[1]]

See also