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
(APNG is done! And ICO is not.)
 
(84 intermediate revisions by 10 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, contain [email protected] or post on the WHATWG mailing list or say something on the #whatwg IRC channel on Freenode.
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]].


== How to edit a spec ==
== Platform ==


We have [[How to write a spec|some documentation on how to write a spec]] that could help if you want to help out.
* [https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html HTML Editing APIs]
* multipart/form-data
* SVG
* ICO (if it contains multiple images, which one is used?)
* 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)
* [[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.)
* 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/20101101063413.bf1d8102.eric@bisonsystems.net)


== Specs to edit ==
== APIs ==


=== DOM ===
* A rewrite of DOM2 Traversal.
* A rewrite of DOM2 Range.
* 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
* [http://developer.mozilla.org/En/DOM/Window.atob window.atob]
** setCapture / releaseCapture [http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/0308.html]
* [http://developer.mozilla.org/En/DOM/Window.btoa window.btoa]
** [http://krijnhoetmer.nl/irc-logs/whatwg/20121128#l-1719 selectstart] (WebKit/IE)
* XMLSerializer()
** https://w3c.github.io/uievents/
* DOMParser()
* Undomanager: http://rniwa.com/editing/undomanager.html and http://rniwa.com/editing/undomanager-usecases.html
* [[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:
* CSS3 Flexible Box or some other UI layout model
* Hit Testing (see http://lists.w3.org/Archives/Public/www-style/2010Aug/0407.html)
* CSS Animation
* Form control styling (see [https://github.com/domenic/html-as-custom-elements HTML as Custom Elements])
* CSS Gradients
* Replaced Content
* [http://dev.w3.org/csswg/cssom/ CSSOM]
** 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 ==
 
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


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


* http://lists.w3.org/Archives/Public/public-html/2008Oct/0127.html (a description of some sections that needed editing in 2008 and how much work they would be)
See also: [[Registries]]


== Other stuff ==
== Other stuff ==


Some notes from the HTML5 spec about things that need doing:
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
** http://perfectionkills.com/the-poor-misunderstood-innerText/
** https://github.com/whatwg/compat/issues/5
** https://html.spec.whatwg.org/multipage/dom.html#the-innertext-idl-attribute
* data: URLs
** https://fetch.spec.whatwg.org/#data-urls
* 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/
* The console.* API
** 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/
** https://console.spec.whatwg.org/
* APNG
** https://w3c.github.io/PNG-spec/


* find object at (x,y) http://msdn.microsoft.com/workshop/author/dhtml/reference/methods/elementfrompoint.asp
[[Category:Spec coordination|*]]
* find mouse position
[[Category:Specification editing]]
* screen object: top left width height pixelDepth colorDepth availWidth availHeight availLeft availTop
* methods/properties for managing scrolling, especially in <textarea>, such as .scrollTop and .scrollHeight in Mozilla
* 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)
* custom syntax highlighting in <textarea>, &lt;pre> (ack Ryan Johnson) (this would probably best be done as some sort of output filter at the CSS level, rather than anything HTML-specific. It would have to support both <textarea>, where the data isn't in the DOM proper, and &lt;pre>, where it is.)

Latest revision as of 13:10, 25 January 2024

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
  • ICO (if it contains multiple images, which one is used?)
  • 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)
  • 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.)
  • 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

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.

Stuff we managed to specify eventually