• HTML

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.

• A number of mailing lists are used for HTML Working Group business, proposals and issues.

Tracker Definitions

• 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.

• W3C Definition of Concensus.

• W3C Voting Policy.

Issue Reference

The list below is a collection of research concerning issues raised on the public-html@w3.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.

Table of Contents:

Table Of Contents

Face to Face Unconference Agenda

Definitions and Clarifications of Terms

• Glossary

• Definitions & Clarification of Terms

  1. Accessibility (definition)

  2. Compatibility (definition)

  3. Fall Back Content (definition)

  4. Universality (definition)

Research Tasks

Research Task List

Use-cases / Problem statements

Accessibility

• Accessibility Dependencies of HTMLx

• Accessibility Testing

• alt Attribute for Critical Content

• Integration of WAI-ARIA into HTML5

• Agreement on accessibility requirements

• headers/id on Tables

• Summary of table contents

• Multimedia Accessibility (Audio Video)

Datetime encoding

• Datetime value

Equivalent Content

• Equivalent content for images

• Availability of equivalent content

• Summary of text fallback

• Examination of current and past browser handling of the OBJECT element

Forms

• Declarative expressions for forms

Semantics

• Abbreviation and Acronym

• Quotes: Reforming & Strengthening a Single Quote Element

• Semantic Markup for Poetic Forms

SVG

• SVG in text/html

Syntax

• Author Syntax

• DOCTYPEs and versioning

Tables

• Problem with authoring complex tables

• From accessibility issues above:

  • Summary of table contents

  • headers/id on Tables

Miscellaneous Issues

• Parsing unknown elements and attributes: A thought experiment in graceful degradation

• Serialization dependent processing differences

• Default style sheet (note plans for a rendering section)

• Method of including style information in document

• Grouping in Definition Lists

• Content Type determination

• Distributed extensibility: (e.g., adding namespace support to text/html serialization)

• Character use in HTML5 Generally about providing additional HTML5 guidance — including document and implementation conformance criteria — for using Unicode characters

Incomplete Issue Descriptions

• Rich text input controls (note contenteditable="")

Solution proposals

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

• Much ado about Q:Proposal to eliminate the Q / BLOCKQUOTE distinction and associating quotations with sources.

• Proposal for eliminating authoring distinctions between block and non-block semantics

Quotations

• Proposal for associating attributions, citations, quotations and references

• New markup attribute on Q and BLOCKQUOTE: "marks"

Key binding mechanism

• A proposal to provide a flexible, international, device independent and cascading key binding mechanism for HTML documents.

Authoring definitions structurally

• Defining terms, variables, proper nouns, and abbreviations

Form/WebApp enhancements

Accessibility enhancements

• A better ALT

• Designating the role of embedded content and providing equivalent text

• Text Alternatives on img

Tables

Miscellaneous

---

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 Proposed Design Principles, Rationales Gathering, and public-html) please update the following index of changed elements and attributes.

Justification for Adding Elements

• subpage

Sectioning and section metadata related

• article (starter page)

• aside (starter page)

• footer (starter page)

• header (starter page)

• nav (starter page)

• section (starter page)

Embedded content related

• embed (starter page)

• figure (starter page)

• video (starter page)

• audio (starter page)

• canvas

Form related

• output (starter page)

• datalist (starter page)

Phrase related

• m (starter page)

• meter (starter page)

• progress (starter page)

• time (starter page)

Others

• command (starter page)

• event-source

• datagrid (starter page)

• details (starter page)

• dialog (starter page)

Justification for Adding Attributes

• subpage

Global attributes

• contenteditable (starter page)

• draggable

• contextmenu (starter page)

• irrelevant (starter page)

Global event attributes

• onevent-name (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

On AREA

• media (starter page)

• ping

• hreflang and rel (starter page)

On A

• media (starter page)

• ping

On BASE

• target (starter page)

On Lists

• value (starter page): on LI

• start (starter page): on OL and UL(?)

On META

• charset (starter page)

UI controls related

• autofocus (starter page)

• form (starter page): also on FIELDSET

• inputmode (starter page)

• replace (starter page)

• data (starter page)

• required (starter page)

• disabled (starter page)

• autocomplete, min, max, pattern and step (starter page)

• repeat (starter page)

• repeat-max (starter page)

• repeat-min (starter page)

• repeat-start (starter page)

• template (starter page)

Added values for INPUT@type

• added attribute values (starter page)

On STYLE

• scoped (starter page)

On SCRIPT

• async (starter page)

On MENU

• type (starter page)

Justification for Changing Attributes

• subpage

Made global

The following attributes were mostly global already in HTML 4.01

• class

• dir

• id

• lang

The following attribute was made much more global (only applying in HTML 4.01 to a few interactive elements):

• tabindex

Justification for Changing Elements

• subpage

Slight element changes

• a (starter page): @href no longer a required attribute

• address (starter page): now scoped

• label (starter page): UA flexibility to match environment/OS UI behavior

• menu(starter page): formerly deprecated in HTML 4.01, now proposed to serve as a contextual menu among other things

Meaning changes

Proposed changes (subtle and not so subtle) in meaning for following elements:

• b (starter page)

• i (starter page)

• small (starter page)

• hr (starter page)

• strong (starter page)

Justification for Dropping Attributes

• subpage

Accessibility related

• accesskey attribute on a, area, button, input, label, legend and textarea

• longdesc attribute on img and iframe

• summary attribute on table

Table related

• axis and abbr attributes on td and th

• headers/id on Tables

• scope attribute on td (starter page)

Metadata related

• profile attribute on head (starter page)

• scheme attribute on meta (starter page)

• version attribute on html (starter page)

• charset and language attributes on script (starter page)

• rev and charset attributes on link and a (starter page)

Associating style sheet data

• style attribute on all elements with the exception of font

Embedding related

• archive, classid, codebase, codetype, declare and standby attributes on object (starter page)

• valuetype and type attributes on param (starter page)

Dropped in favor of @id for a unique identifier

• name attribute on map, img, object, form, iframe, a (use id instead) (starter page)

Frame/iframe related

• target attribute on link (starter page)

Client-side image-map related

• nohref attribute on area (starter page)

• shape and coords attributes on a (starter page)

Justification for Dropping Presentational Attributes

• subpage

Not Previously deprecated

• size attribute on input and select (starter page)

table related

• align attribute on col, colgroup, tbody, td, tfoot, th, thead, and tr (starter page)

• border attribute on table (starter page)

• cellpadding and cellspacing attributes on table (starter page)

• char and charoff attributes on col, colgroup, tbody, td, tfoot, th, thead and tr (starter page)

• frame attribute on table (starter page)

• rules attribute on table (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)

iframe related

• frameborder attribute on iframe (starter page)

• height attribute on iframe (starter page)

• marginheight and marginwidth attributes on iframe (starter page)

• scrolling attribute on iframe (starter page)

Previously deprecated

• 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)

• background attribute on body (starter page)

• bgcolor attribute on table, tr, td, th and body (starter page)

• border attribute on img and object (starter page)

• clear attribute on br (starter page)

• compact attribute on dl, menu, ol and ul (starter page)

• noshade attribute on hr (starter page)

• hspace and vspace attributes on img and object (starter page)

• nowrap attribute on td and th (starter page)

• size attribute on hr (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

• subpage

Not Previously deprecated

• acronym: very similar and overlapping semantics with ABBR

• noscript (starter page): this is only dropped from the XML serialization, though explanation for creating this difference in serializations is needed.

frame related

• frame (starter page)

• frameset (starter page)

• noframes (starter page)

Previously deprecated

• applet (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.

• dir (starter page)

• isindex (starter page)

Previously deprecated presentation elements

• basefont (starter page)

• big (starter page)

• center (starter page)

• font (starter page)

• s (starter page)

• strike (starter page)

• tt (starter page)

• u (starter page)

---

See also

• Agenda/issues maintained by the HTML WG chair

• HTML Slicing Tutorial

• HTMLAsSheAreSpoke

• HTML/SpecReviews

• User Agents

• Research tasks

Design Documents

• Proposed design principles

• Popular uses for forms on the web

• Proposal for Chained Classnames

• Scope of <audio> and <video> elements

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)