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
(→‎APIs: UI Events spec)
(90 intermediate revisions by 9 users not shown)
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, contact [email protected], post on the WHATWG mailing list or say something on [[IRC]].


* 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:
== Platform ==
** 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.)


* [https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html HTML Editing APIs]
* 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)


These sections of HTML5 could easily be taken out and make into independent specs:
== APIs ==
* 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


* User Interaction Events (onclick, onkeypress, etc).
** e.g. need to define somewhere that if you cancel mousedown, an element can't get focus
** 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)
** https://w3c.github.io/uievents/
* 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/[email protected]
** http://sideshowbarker.github.com/console-spec/]
* [[DOM XPath]]
* [[DOM XSLTProcessor]]


These specs currently have active editors, but have historically spent time abandoned:
== CSS ==
* DOM3 Events
* Keyboard Events -- .charCode, .keyCode, and related stuff (mostly defining legacy interfaces)
* setTimeout
* 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.


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
** 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


See also:
== Registries ==
* http://lists.w3.org/Archives/Public/public-html/2008Oct/0127.html which lists (ordered here by total time estimated):
 
** altss - 300h over 2y
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:
** url - 300h over 2y to 1260h over 3y
 
** common dom - 620h over 3y
* MIME types
** sniffing - 890h over 3y
* URL schemes
** undo - 940h over 4y
 
** events - 1050h over 4y
It's possible that the right solution is to change approach altogether (e.g. moving more to a wiki model of registries).
** 2d - 1230h over 4y
 
** 3d - 1570h over 4y
See also: [[Registries]]
** rendering - 2740h over 4y
 
** window - 5300h over 4y
== Miscellaneous ==
* [[Needs specification]]
* 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.)
* 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)
* Client-side HTTP implementation requirements specification ("option 3" in http://www.w3.org/mid/[email protected])
* <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 ==
 
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:
 
* 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
 
[[Category:Spec coordination|*]]
[[Category:Specification editing]]

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