Difference between revisions of "Specs/todo"
(New page: 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 ed...)
(Move stuff around, especially into a new "Stuff we managed to specify eventually" section)
|(106 intermediate revisions by 10 users not shown)|
|Line 1:||Line 1:|
many specifications that of the . you want to ,
[http://www.w3.org/Style/CSS/current-work specifications for extending CSSthat are in need of editors.
that the .
Latest revision as of 17:54, 21 June 2021
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.
- HTML Editing APIs
- APNG (other image formats too maybe?)
- 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)
- 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.)
- HTTP (error handling in particular, might become less of an issue if we're successful in removing it in favor of HTTPS)
- Client-side HTTP implementation requirements specification ("option 3" in http://www.w3.org/mid/[email protected])
- User Interaction Events (onclick, onkeypress, etc).
- Undomanager: http://rniwa.com/editing/undomanager.html and http://rniwa.com/editing/undomanager-usecases.html
- DOM XPath
- DOM XSLTProcessor
There are 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 HTML as Custom Elements)
- 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
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
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.
Stuff we managed to specify eventually
- innerText and outerText
- data: URLs
- Table Layout
- The console.* API