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).
Rationale: Difference between revisions
(change wording to be clear that <image> isn't a FF/Opera thing. Change plaintext to show its origins more accurately) |
No edit summary |
||
| Line 17: | Line 17: | ||
<image> element is treated as an alternate (but invalid) name for <img>. This is because some sites (around 0.2%) make this mistake. It is already treated as an image by most major browsers. | <image> element is treated as an alternate (but invalid) name for <img>. This is because some sites (around 0.2%) make this mistake. It is already treated as an image by most major browsers. | ||
=== Meter and Progress === | |||
[ temp save ] | |||
== References == | == References == | ||
Revision as of 18:05, 5 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.
Other Pages
- Why no namespaces
- Why no script implements
- Why not reuse legend or another mini-header element.
- Rationale for a variety of elements
Specific Elements
Plaintext
the <plaintext> element is a obsolete precursor to the <pre> element.[1] 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
<image> element is treated as an alternate (but invalid) name for <img>. This is because some sites (around 0.2%) make this mistake. It is already treated as an image by most major browsers.
Meter and Progress
[ temp save ]
References