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)
m (Flexbox is being edited; Add link)
Line 14: Line 14:
 
* A rewrite of DOM2 Range.
 
* A rewrite of DOM2 Range.
 
** including much more detail
 
** including much more detail
** including de-facto features, e.g. createContextualFragment()
+
** including de-facto features, e.g. [https://developer.mozilla.org/en/DOM/range.createContextualFragment createContextualFragment()]
 
* 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
Line 26: Line 26:
  
 
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:
* CSS3 Flexible Box or some other UI layout model
 
 
* CSS Animation
 
* CSS Animation
 
* CSS Gradients
 
* CSS Gradients

Revision as of 16:57, 5 June 2010

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 or post on the WHATWG mailing list or say something on the #whatwg IRC channel on Freenode.

How to edit a spec

We have some documentation on how to write a spec that could help if you want to help out.

Specs to edit

DOM

  • Web DOM Core is looking for an editor (http://simon.html5.org/specs/web-dom-core)
    • should document.documentURI really exist? be readonly?
  • A rewrite of DOM2 Traversal.
  • A rewrite of DOM2 Range.
  • User Interaction Events (onclick, onkeypress, etc).
    • e.g. need to define somewhere that if you cancel mousedown, an element can't get focus
  • window.atob
  • window.btoa
  • XMLSerializer()
  • DOMParser()
  • An API for cryptography, to generate keys and the like

CSS

There are many specifications for extending CSS that are in need of editors. The most important ones are:

  • CSS Animation
  • CSS Gradients
  • CSSOM
    • CSSOM needs to define how Link:, <?xml-stylesheet?>, <link rel=stylesheet>, and <style> interact with the fetching algorithm, the event loop, and the parsers from HTML5.
    • CSSOM should have a mechanism for taking elements full-screen
    • it has been proposed that CSSOM have a mechanism for keeping track of when expensive-to-compute areas of the document (e.g. a canvas) are actually being rendered.
      • Add a pair of events that fire when an element is hidden and unhidden
      • Add a pair of events that fire when an element is scrolled into and out of the view
  • <?xml-stylesheet?> could do with a rewrite for integration with CSSOM; do 'load' and 'error' events fire on it?

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:

It's possible that the right solution is to change approach altogether (e.g. moving more to a wiki model of registries).

MISC

  • 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.)
  • JS changes: http://wiki.whatwg.org/wiki/Web_ECMAScript

See also

Other stuff

Some notes from the HTML5 spec about things that need doing: