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

Difference between revisions of "Rationale"

From WHATWG Wiki
Jump to navigation Jump to search
m (Add note)
Line 38: Line 38:
=== B, U, EM, and STRONG ===
=== B, U, EM, and STRONG ===
-- temporary stub --
-- temporary stub --
== Notes ==
* <code>&lt;meta http-equiv=content-language></code>: http://lists.w3.org/Archives/Public/public-html/2008Aug/0300.html

== Other Pages ==
== Other Pages ==

Revision as of 18:39, 8 May 2010

This document serves a rationale document for various parts of the HTML5 specification. Over time this page will be a complete rationale document.

General Rationale

One Vendor, One Veto

Part of the the goal of the WHATWG is to document how web browsers actually handle HTML. As such browser vendors already have veto power - by not following the standard. The W3C and WHATWG do not have any enforcement power and can only write what browsers are willing to implement. Not removing features from the HTML standard that at least one browser vendor has stated they are unwilling to implement causes the HTML spec to not accurately document reality.[1][2]

Specific Elements


the <plaintext> element is a obsolete precursor to the <pre> element. [3] It is is now in the HTML5 spec as a method of stopping all further html token parsing. It lacks an end tag and just emits the rest of the page as plain text. It throws a parse error upon reaching the end of the document as it is not considered a valid element (and it is missing an end-tag).


<image> element is treated as an alternate (but invalid) name for <img>. This is because some sites (around 0.2%[4]) make this mistake. It is already treated as an image by most major browsers.

Meter and Progress (are not the same thing)

<meter> is not just a special case of <progress>. The meter element represents a scalar measurement within a known range, such as storage quota usage, a relative popularity rating or relevance indicator. The control allows for the indication of high and low ranges, or minimum, maximum and optimal levels.

The progress element, on the other hand, represents the completion progress of a task. This could be a real time indicator for background processing task (e.g. using Web Workers or a file upload). Progress elmements can also be in the indeterminate state, indicating that something is in progress, but it's completion progress is unknown.

The default rendering for a meter element could look something like the following:

<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_leveldiscrete.gif" alt="example of proper rendering for the meter element">

Whereas, the default rendering for the progress element could look like this:

<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_determprogsizes.jpg">

Alternatively, an indeterminate progress bar could also be styled as a throbber, which indicates progress without any indication of the remaining progress:

<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_asynchprogindsizes.jpg" alt="picture of the default apple throbber">

See Re: <progress> draft for details.

B, U, EM, and STRONG

-- temporary stub --


Other Pages