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
(Update)
(→‎APIs: Console API has an active spec)
Line 19: Line 19:
** [http://krijnhoetmer.nl/irc-logs/whatwg/20121128#l-1719 selectstart] (WebKit/IE)
** [http://krijnhoetmer.nl/irc-logs/whatwg/20121128#l-1719 selectstart] (WebKit/IE)
* 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
* The console.* API.
* <del>The console.* API.</del>
** https://console.spec.whatwg.org/
** https://github.com/DeveloperToolsWG/console-object
** https://github.com/DeveloperToolsWG/console-object
** http://www.w3.org/Bugs/Public/show_bug.cgi?id=10694
** http://www.w3.org/Bugs/Public/show_bug.cgi?id=10694

Revision as of 09:15, 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: