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
(CSS: Added Table Layout)
(APIs: UI Events spec)
 
(31 intermediate revisions by 7 users not shown)
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]].
 
 
See also: [[Specs|Specs with editors]], [[Howto spec]].
 
  
 
== 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
+
* multipart/form-data
 +
* SVG
 +
* APNG (other image formats too maybe?)
 +
* [[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?)
 +
* HTTP (error handling in particular, might become less of an issue if we're successful in removing it in favor of HTTPS)
  
 
== APIs ==
 
== APIs ==
Line 12: Line 16:
 
* User Interaction Events (onclick, onkeypress, etc).
 
* User Interaction Events (onclick, onkeypress, etc).
 
** e.g. need to define somewhere that if you cancel mousedown, an element can't get focus
 
** e.g. need to define somewhere that if you cancel mousedown, an element can't get focus
* An API for cryptography, to generate keys and the like
+
** setCapture / releaseCapture [http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/0308.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/]
+
** [http://krijnhoetmer.nl/irc-logs/whatwg/20121128#l-1719 selectstart] (WebKit/IE)
* setCapture / releaseCapture [http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/0308.html]
+
** https://w3c.github.io/uievents/
 
* Undomanager: http://rniwa.com/editing/undomanager.html and http://rniwa.com/editing/undomanager-usecases.html
 
* Undomanager: http://rniwa.com/editing/undomanager.html and http://rniwa.com/editing/undomanager-usecases.html
 +
* <del>The console.* API.</del>
 +
** https://console.spec.whatwg.org/
 +
** https://github.com/DeveloperToolsWG/console-object
 +
** 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/]
 
* [[DOM XPath]]
 
* [[DOM XPath]]
 +
* [[DOM XSLTProcessor]]
  
 
== 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:
 +
* Hit Testing (see http://lists.w3.org/Archives/Public/www-style/2010Aug/0407.html)
 +
* Form control styling (see [https://github.com/domenic/html-as-custom-elements HTML as Custom Elements])
 
* Table Layout
 
* Table Layout
 +
** http://dbaron.org/css/intrinsic/
 +
** http://dev.w3.org/csswg/css3-tables-algorithms/Overview.src.htm
 +
** https://drafts.csswg.org/css-tables-3/
 +
* Replaced Content
 +
** 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
  
 
== Registries ==
 
== Registries ==
Line 28: Line 47:
  
 
* 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).
Line 34: Line 53:
 
See also: [[Registries]]
 
See also: [[Registries]]
  
== MISC ==
+
== Miscellaneous ==
 
* an API to do syntax highlighting on  &lt;textarea>, &lt;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  &lt;textarea>, &lt;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 [[GIF]]s 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)
* 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)
 
* 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
+
* <del>innerText and</del> outerText, if browsers don't remove them entirely
 +
** http://perfectionkills.com/the-poor-misunderstood-innerText/
 +
** https://github.com/whatwg/html/issues/465
 +
* data URLs
 +
** https://simonsapin.github.io/data-urls/
  
 
== Other stuff ==
 
== Other stuff ==
Line 47: Line 69:
 
Some notes from the HTML5 spec about things that need doing:
 
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)
 
* 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)
 
** Maybe something like moz-icon://? http://lists.w3.org/Archives/Public/public-webapps/2010JanMar/0255.html, http://draft-icon-uri-scheme.googlecode.com/hg/draft-lafayette-icon-uri-scheme-00.html
 
** Maybe something like moz-icon://? http://lists.w3.org/Archives/Public/public-webapps/2010JanMar/0255.html, http://draft-icon-uri-scheme.googlecode.com/hg/draft-lafayette-icon-uri-scheme-00.html
  
[[Category:Spec_coordination]]
+
[[Category:Spec coordination|*]]
 +
[[Category:Specification editing]]

Latest revision as of 09:31, 15 March 2016

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
  • SVG
  • 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?)
  • HTTP (error handling in particular, might become less of an issue if we're successful in removing it in favor of HTTPS)

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

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: