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
(Platform: Modern robots.txt behavior should be recorded and standardized.)
(move big ticket items to the top within their category)
Line 3: Line 3:
 
== Platform ==
 
== 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.)
+
* [https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html HTML Editing APIs]
* X-Frames-Options (seems this is going into CSP)
 
 
* multipart/form-data
 
* multipart/form-data
 
* HTTP (error handling in particular)
 
* HTTP (error handling in particular)
 
* APNG (other image formats too maybe?)
 
* APNG (other image formats too maybe?)
* HTML editing: the spec is quite mature, but needs more work
 
 
* [[Wikipedia:Robots.txt|robots.txt]]
 
* [[Wikipedia:Robots.txt|robots.txt]]
 +
* A specification that defines how XML maps to DOM Core. (This could be in DOM Parsing and Serialization or HTML if XML does not get updated.)
 +
* X-Frames-Options (make part of CSP?)
  
 
== APIs ==
 
== APIs ==
Line 17: Line 17:
 
** setCapture / releaseCapture [http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/0308.html]
 
** setCapture / releaseCapture [http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/0308.html]
 
** [http://krijnhoetmer.nl/irc-logs/whatwg/20121128#l-1719 selectstart] (WebKit/IE)
 
** [http://krijnhoetmer.nl/irc-logs/whatwg/20121128#l-1719 selectstart] (WebKit/IE)
* An API for cryptography, to generate keys and the like
+
* Undomanager: http://rniwa.com/editing/undomanager.html and http://rniwa.com/editing/undomanager-usecases.html
 
* The console.* API. [http://www.w3.org/Bugs/Public/show_bug.cgi?id=10694] [http://www.w3.org/mid/d7be01cb7077$4dd45010$e97cf030$@gmail.com] [http://sideshowbarker.github.com/console-spec/]
 
* The console.* API. [http://www.w3.org/Bugs/Public/show_bug.cgi?id=10694] [http://www.w3.org/mid/d7be01cb7077$4dd45010$e97cf030$@gmail.com] [http://sideshowbarker.github.com/console-spec/]
* Undomanager: http://rniwa.com/editing/undomanager.html and http://rniwa.com/editing/undomanager-usecases.html
 
 
* [[DOM XPath]]
 
* [[DOM XPath]]
  
Line 25: Line 24:
  
 
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:
 +
* Hit Testing (see http://lists.w3.org/Archives/Public/www-style/2010Aug/0407.html)
 +
* Form control styling (see [https://github.com/dglazkov/html-as-custom-elements HTML as Custom Elements])
 
* Table Layout
 
* Table Layout
 
** http://dbaron.org/css/intrinsic/
 
** http://dbaron.org/css/intrinsic/
Line 31: Line 32:
 
** http://dev.w3.org/csswg/css3-content/ (Do we still want this or is the component model sufficient?)
 
** http://dev.w3.org/csswg/css3-content/ (Do we still want this or is the component model sufficient?)
 
* an imperative model of box-tree construction
 
* an imperative model of box-tree construction
* hit testing per http://lists.w3.org/Archives/Public/www-style/2010Aug/0407.html
 
  
 
== Registries ==
 
== Registries ==
Line 38: Line 38:
  
 
* MIME types
 
* MIME types
* Schemes
+
* URL schemes
  
 
It's possible that the right solution is to change approach altogether (e.g. moving more to a wiki model of registries).
 
It's possible that the right solution is to change approach altogether (e.g. moving more to a wiki model of registries).

Revision as of 12:38, 10 April 2014

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.

Platform

  • HTML Editing APIs
  • multipart/form-data
  • HTTP (error handling in particular)
  • APNG (other image formats too maybe?)
  • robots.txt
  • A specification that defines how XML maps to DOM Core. (This could be in DOM Parsing and Serialization or HTML if XML does not get updated.)
  • X-Frames-Options (make part of CSP?)

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
  • URL 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

Miscellaneous

  • 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.)
  • Animated GIFs need a spec that, in particular, specifies how to handle timings (not all browsers honor all values, so we should specify what needs to be honored 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: