Main Page

From HTML WG Wiki
Revision as of 03:33, 13 August 2013 by Gadams (Talk | contribs)

Jump to: navigation, search

Resources

Meetings

The HTML WG holds regular telcons and face-to-face meetings.

Our meetings minutes are publicly available.

Some general information about HTML WG meetings is documented in the Phone Meetings & Face-to-Face Meetings sections of the HTML WG home page. (could be moved here)

HTML Working Group Issues


Contents


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

Change Proposals

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.

Definitions and Clarifications of Terms

Research Tasks

ResearchNeeds

Use-cases / Problem statements

Accessibility

Datetime encoding

Equivalent Content

Forms

Semantics

SVG

Syntax

Tables

Miscellaneous Issues

Incomplete Issue Descriptions

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

Quotations

Key binding mechanism

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

Authoring definitions structurally

Form/WebApp enhancements

Accessibility enhancements

Tables

Media

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 ProposedDesignPrinciples, RationalesGathering, and public-html) please update the following index of changed elements and attributes.

Justification for Adding Elements

Sectioning and section metadata related

Embedded content related

Form related

Phrase related

Others

Justification for Adding Attributes

Global attributes

Global event attributes

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

On A

On BASE

On Lists

On META

UI controls related

Added values for INPUT@type

On STYLE

On SCRIPT

On MENU

Justification for Changing Attributes

Made global

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

Meaning changes

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

Justification for Dropping Attributes

Accessibility related

Table related

Metadata related

Associating style sheet data

Embedding related

Dropped in favor of @id for a unique identifier

Frame/iframe related

Client-side image-map related

Justification for Dropping Presentational Attributes

Not Previously deprecated

table related
iframe related

Previously deprecated

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.
frame related

Previously deprecated

Previously deprecated presentation elements


See also

Design Documents

HTML5 online tools