- Change Proposals
- HTML Accessibility Task Force
- Testing Task Force
- Extension Specifications (and How to write one)
Our meetings minutes are publicly available.
HTML Working Group Issues
- Tracker is a HTML Working Group issue, action and resolution tracking tool.
- Teleconferences are typically used to facilitate issue coordination with Minutes announced via the announce mailing list.
- Surveys are a working group tool to aid information gathering and if needed decision making. For more information visit decision history.
- EmailLists are used for HTML Working Group business, proposals and issues.
- TaskForces exist for specialized issues and work.
- 1 Resources
- 2 Meetings
- 3 HTML Working Group Issues
- 4 Research Tasks
- 5 Use-cases / Problem statements
- 6 Solution proposals
- 7 Use-cases / Problem statements for changes in the draft
- 7.1 Justification for Adding Elements
- 7.2 Justification for Adding Attributes
- 7.3 Justification for Changing Attributes
- 7.4 Justification for Changing Elements
- 7.5 Justification for Dropping Attributes
- 7.6 Justification for Dropping Presentational Attributes
- 7.7 Justification for Dropping Elements
- 8 See also
- ISSUE = A topic of concern or a problem. (An issue defines a problem.)
- ACTION = The process of doing something in order to resolve or help resolve an ISSUE. (An ACTION generates a potential resolution to an ISSUE, or helps solve it e.g. by gathering more information.)
Tracker Issue State Definitions
- RAISED = A working group member suggests this is worth a WG discussion and potentially a decision, but to date no concrete proposal has been created that enjoys a consensus of at least one.
- OPEN = At least one concrete proposal has been made resolving this issue, but one on which consensus has either not been evaluated, or has not yet been reached; a working group member is assigned an ACTION to follow up (similar to ASSIGNED).
- PENDINGREVIEW = An Editor has reviewed arguments and edited spec to taste, or the WG chairs have evaluated the level of consensus and identified one or more proposals that would resolve the issue. In the case where multiple proposals are identified, the Editors may make the determination as to which one to incorporate.
- POSTPONED = The WG has decided the issue will not be addressed at this time due to engineering constraints, cost-effectiveness, or the inability of the issue to be address in the time defined by our charter. To be investigated during the next chartering period.
- CLOSED = The chairs believe either the WG has resolved the issue (via spec editing) or the issue has been withdrawn. Only the chairs should move issues to 'closed'. Typically moving issues from PENDINGREVIEW to CLOSED will involve review in the weekly telecon.
Tracker Action State Definitions
- OPEN = A working group member has been assigned this ACTION, and has clear steps to follow up (an action cannot be created without assigning to someone).
- PENDINGREVIEW = The person to whom the action was assigned has further information or a recommendation, and wishes the WG and chairs to review it. This may also be used to flag a status update, but then move back to OPEN (e.g., an assignee wants to get on the agenda for the weekly telecon to give a status update, but then still has more to do to complete the action.
- CLOSED = The chairs believe either the action was withdrawn or it has been completed. Only the chairs should move actions to 'closed'. Typically moving actions from PENDINGREVIEW to CLOSED will involve review in the weekly telecon.
Issue Resolution Related Policies
- HTML Working Group Decision Policy (in Charter) - 2007.
- HTML Working Group Decision Policy - Began use Fall 2009.
- W3C Definition of Consensus.
- W3C Voting Policy.
The list below is a collection of research concerning issues raised on the firstname.lastname@example.org mailing list (archive). Please follow the issue template when creating new reference pages, including adding links to all the related e-mails in the discussion. Be sure to document issues in a way that the editors will pay attention to them.
Definitions and Clarifications of Terms
Use-cases / Problem statements
- Multimedia Accessibility (Audio Video)
- Parsing unknown elements and attributes: A thought experiment in graceful degradation
- DefaultStyleSheet05 (note plans for a rendering section)
- DistributedExtensibility: (e.g., adding namespace support to text/html serialization)
- HTMLCharacterUsage Generally about providing additional HTML5 guidance — including document and implementation conformance criteria — for using Unicode characters
Incomplete Issue Descriptions
- RichTextInput03 (note contenteditable="")
Since solutions are sometimes designed to address multiple problems, it will be useful to create hyperlinked pages describing solutions and proposed solutions that link to problem statement/ use-cases pages. Likewise, the use-case pages should link to proposed solution pages and the HTML5 draft and elsewhere.
General document enhancements
- MuchAdoAboutQ:Proposal to eliminate the Q / BLOCKQUOTE distinction and associating quotations with sources.
- Proposal for associating attributions, citations, quotations and references
- New markup attribute on Q and BLOCKQUOTE: "marks"
Key binding mechanism
- KeyBindingMarkup to provide a flexible, international, device independent and cascading key binding mechanism for HTML documents.
Authoring definitions structurally
Use-cases / Problem statements for changes in the draft
The HTML 5 differences from HTML 4 draft enumerates a number of attributes and elements that are different between the two specifications, but it gives little by way of rationale for the changes. As rationale for changes emerges (see ProposedDesignPrinciples, RationalesGathering, and public-html) please update the following index of changed elements and attributes.
Justification for Adding Elements
- AddedElementArticle (starter page)
- AddedElementAside (starter page)
- AddedElementFooter (starter page)
- AddedElementHeader (starter page)
- AddedElementNav (starter page)
- AddedElementSection (starter page)
- AddedElementEmbed (starter page)
- AddedElementFigure (starter page)
- AddedElementVideo (starter page)
- AddedElementAudio (starter page)
- AddedElementM (starter page)
- AddedElementMeter (starter page)
- AddedElementProgress (starter page)
- AddedElementTime (starter page)
- AddedElementCommand (starter page)
- AddedElementDatagrid (starter page)
- AddedElementDetails (starter page)
- AddedElementDialog (starter page)
Justification for Adding Attributes
- AddedAttributeContenteditable (starter page)
- AddedAttributeContextmenu (starter page)
- AddedAttributeIrrelevant (starter page)
Global event attributes
- AddedAttributeOneventname (starter page)
And the other new global event attributes: onabort, onbeforeunload, onblur, onchange, oncontextmenu, ondrag, ondragend, ondragenter, ondragleave, ondragover, ondragstart, ondrop, onerror, onfocus, onkeydown, onkeypress, onkeyup, onload, onmessage, onmousewheel, onresize, onscroll, onselect, onsubmit, onunload
- AddedAttributetarget (starter page)
- AddedAttributeCharset (starter page)
- AddedAttributeAutofocus (starter page)
- AddedAttributeForm (starter page): also on FIELDSET
- AddedAttributeInputmode (starter page)
- AddedAttributeReplace (starter page)
- AddedAttributeData (starter page)
- AddedAttributeRequired (starter page)
- AddedAttributeDisabled (starter page)
- autocomplete, min, max, pattern and step (starter page)
- AddedAttributeRepeat (starter page)
- AddedAttributeRepeatmax (starter page)
- AddedAttributeRepeatmin (starter page)
- AddedAttributeRepeatstart (starter page)
- AddedAttributeTemplate (starter page)
Added values for INPUT@type
- AddedAttributeValues (starter page)
- AddedAttributeScoped (starter page)
- AddedAttributeAsync (starter page)
- AddedAttributeType (starter page)
Justification for Changing Attributes
The following attributes were mostly global already in HTML 4.01
The following attribute was made much more global (only applying in HTML 4.01 to a few interactive elements):
Justification for Changing Elements
Slight element changes
- ChangedElementA (starter page): @href no longer a required attribute
- ChangedElementAddress (starter page): now scoped
- ChangedElementLabel (starter page): UA flexibility to match environment/OS UI behavior
- ChangedElementMenu(starter page): formerly deprecated in HTML 4.01, now proposed to serve as a contextual menu among other things
Proposed changes (subtle and not so subtle) in meaning for following elements:
- ChangedElementB (starter page)
- ChangedElementI (starter page)
- ChangedElementSmall (starter page)
- ChangedElementHr (starter page)
- ChangedElementStrong (starter page)
Justification for Dropping Attributes
- accesskey attribute on a, area, button, input, label, legend and textarea
- DroppedAttributeProfile (starter page)
- DroppedAttributeScheme (starter page)
- DroppedAttributeVersion (starter page)
- DroppedAttributeCharset (starter page)
- DroppedAttributeRev (starter page)
Associating style sheet data
- archive, classid, codebase, codetype, declare and standby attributes on object (starter page)
- DroppedAttributeValuetype (starter page)
Dropped in favor of @id for a unique identifier
- DroppedAttributeTarget (starter page)
Justification for Dropping Presentational Attributes
Not Previously deprecated
- DroppedAttributeSize (starter page)
- align attribute on col, colgroup, tbody, td, tfoot, th, thead, and tr (starter page)
- DroppedAttributeBorder (starter page)
- DroppedAttributeCellpadding (starter page)
- char and charoff attributes on col, colgroup, tbody, td, tfoot, th, thead and tr (starter page)
- DroppedAttributeFrame (starter page)
- DroppedAttributeRules (starter page)
- valign attribute on col, colgroup, tbody, td, tfoot, th, thead and tr (starter page)
- width attribute on table, col, colgroup, and iframe (starter page)
- DroppedAttributeFrameborder (starter page)
- DroppedAttributeHeight (starter page)
- DroppedAttributeMarginheight (starter page)
- DroppedAttributeScrolling (starter page)
- align attribute on caption, iframe, img, input, object, legend, table, hr, div, h1, h2, h3, h4, h5, h6, p, and body (starter page)
- alink, link, text and vlink attributes on body (starter page)
- DroppedAttributeBackground (starter page)
- bgcolor attribute on table, tr, td, th and body (starter page)
- DroppedAttributeBorder (starter page)
- DroppedAttributeClear (starter page)
- compact attribute on dl, menu, ol and ul (starter page)
- DroppedAttributeNoshade (starter page)
- DroppedAttributeHspace (starter page)
- DroppedAttributeNowrap (starter page)
- DroppedAttributeSize (starter page)
- type attribute on li, ol and ul (starter page)
- width attribute on hr, td, th, and pre (starter page)
Justification for Dropping Elements
Not Previously deprecated
- AbbrAcronym01: very similar and overlapping semantics with ABBR
- DroppedElementNoscript (starter page): this is only dropped from the XML serialization, though explanation for creating this difference in serializations is needed.
- DroppedElementFrame (starter page)
- DroppedElementFrameset (starter page)
- DroppedElementNoframes (starter page)
- DroppedElementApplet (starter page): while previously deprecated the semantic differentiation of objects through an element such as applet has been reintroduced with canvas, embed, video and audio.
- DroppedElementDir (starter page)
- DroppedElementIsindex (starter page)
Previously deprecated presentation elements
- DroppedElementBasefont (starter page)
- DroppedElementBig (starter page)
- DroppedElementCenter (starter page)
- DroppedElementFont (starter page)
- DroppedElementS (starter page)
- DroppedElementStrike (starter page)
- DroppedElementTt (starter page)
- DroppedElementU (starter page)
- HTML Slicing Tutorial
- Last Call Timeline and Action Plan
HTML5 online tools
- HTML5Lib based parse tree Enter a publicly available URL to see the parse tree.
- Another parse tree viewer using the Validor.nu HTML parser (in Java) Enter a publicly available URL to see the parse tree.
- HTML5Lib Versatile tool for parsing HTML serialization according to HTML5 (draft) parsing rules (i.e., parses well-formed and ill-formed HTML).
- Live DOM Viewer (text/html) Paste, or compose HTML and watch how your current browser parses the source into a DOM tree.
- Live DOM Viewer (XML) Same as prior, but for XML parsing (currently broken, please help)