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
m (moved Specifications TODO to Specs todo: better title)
Line 1: Line 1:
 
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]]. [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-May/031666.html This mailing list post] has some advice on the matter.
 
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]]. [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-May/031666.html This mailing list post] has some advice on the matter.
  
See also: [[Specs|Specs with editors]]
+
See also: [[Specs|Specs with editors]], [[Howto spec]].
  
== How to edit a spec ==
+
== Platform ==
 
 
We have [[How to write a spec|some documentation on how to write a spec]] that could help if you want to help out.
 
 
 
== Specs to edit ==
 
 
 
=== 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.)
 
* 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
 
* X-Frames-Options
  
=== APIs ===
+
== APIs ==
  
 
* User Interaction Events (onclick, onkeypress, etc).
 
* User Interaction Events (onclick, onkeypress, etc).
Line 24: Line 18:
 
* [[DOM XPath]]
 
* [[DOM XPath]]
  
=== CSS ===
+
== CSS ==
  
 
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:
 
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:
Line 31: Line 25:
 
* [http://dev.w3.org/csswg/cssom/ CSSOM] — see http://wiki.csswg.org/spec/cssom
 
* [http://dev.w3.org/csswg/cssom/ CSSOM] — see http://wiki.csswg.org/spec/cssom
  
=== Registries ===
+
== 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:
 
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:
Line 42: Line 36:
 
See also: [[Registries]]
 
See also: [[Registries]]
  
=== MISC ===
+
== MISC ==
 
* an API to do syntax highlighting on  <textarea>, <pre>, and contenteditable sections would be highly popular with Web developers (ack Ryan Johnson). (This would probably best be done as some sort of output filter at the CSS level, rather than anything HTML-specific.)
 
* an API to do syntax highlighting on  <textarea>, <pre>, and contenteditable sections would be highly popular with Web developers (ack Ryan Johnson). (This would probably best be done as some sort of output filter at the CSS level, rather than anything HTML-specific.)
 
* JS changes: [[Web ECMAScript]]
 
* JS changes: [[Web ECMAScript]]
Line 49: Line 43:
 
* innerText and outerText, if browsers don't remove them entirely
 
* innerText and outerText, if browsers don't remove them entirely
  
== See also ==
+
== Other stuff ==
  
* 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)
+
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.
 
 
== Other stuff ==
 
  
 
Some notes from the HTML5 spec about things that need doing:
 
Some notes from the HTML5 spec about things that need doing:

Revision as of 16:25, 14 June 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. This mailing list post has some advice on the matter.

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

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

  • an API to do syntax highlighting on <textarea>, <pre>, and contenteditable sections would be highly popular with Web developers (ack Ryan Johnson). (This would probably best be done as some sort of output filter at the CSS level, rather than anything HTML-specific.)
  • 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)
  • 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

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: