- From: Simon Pieters via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 05 Mar 2012 09:54:12 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html4-differences In directory hutz:/tmp/cvs-serv7388 Modified Files: Overview.src.html Log Message: fix changed elements Index: Overview.src.html =================================================================== RCS file: /sources/public/html5/html4-differences/Overview.src.html,v retrieving revision 1.151 retrieving revision 1.152 diff -u -d -r1.151 -r1.152 --- Overview.src.html 2 Mar 2012 15:22:25 -0000 1.151 +++ Overview.src.html 5 Mar 2012 09:54:10 -0000 1.152 @@ -700,15 +700,62 @@ useful:</p> <ul> + <!-- <li><p>The <code data-anolis-spec=html>a</code> element without an <code data-anolis-spec=html title=attr-hyperlink-href>href</code> attribute now represents a placeholder for where a link otherwise might have been placed.</p></li> + + html4: + Each A element defines an anchor + + 1. The A element's content defines the position of the anchor. + 2. The name attribute names the anchor so that it may be the destination + of zero or more links (see also anchors with id). + 3. The href attribute makes this anchor the source anchor of exactly one + link. + + Authors may also create an A element that specifies no anchors, i.e., that + doesn't specify href, name, or id. Values for these attributes may be set + at a later time through scripts. + + html5: + If the a element has an href attribute, then it represents a hyperlink (a + hypertext anchor). + + If the a element has no href attribute, then the element represents a + placeholder for where a link might otherwise have been placed, if it had + been relevant. + + Both basically say that <a> without href is a "placeholder", so this isn't + really a change. + --> + + <!-- + <li><p>The <code data-anolis-spec=html>abbr</code> element now represents + an abbreviation <em>or</em> an acronym. + + html4: + Indicates an abbreviated form (e.g., WWW, HTTP, URI, Mass., etc.). + html5: + The abbr element represents an abbreviation or acronym, optionally with + its expansion. + + Not a major change (technically acronym is a form of abbreviation anyway), + and this document says to use abbr instead of acronym already. + --> + <li><p>The <code data-anolis-spec=html>address</code> element is now scoped by the nearest ancestor <code data-anolis-spec=html>article</code> or <code data-anolis-spec>body</code> element.</p></li> + <!-- + AREA + html4 doesn't really have a definition of area, but html5 does, but that's + hardly worth calling out here. + --> + <li><p>The <code data-anolis-spec=html>b</code> element now represents a span of text to which attention is being drawn for utilitarian purposes without conveying any extra importance and with no implication of an @@ -716,6 +763,83 @@ names in a review, actionable words in interactive text-driven software, or an article lede.</p></li> + <!-- + BASE + html4: + The BASE element allows authors to specify a document's base URI + explicitly. + + html5: + The base element allows authors to specify the document base URL for the + purposes of resolving relative URLs, and the name of the default browsing + context for the purposes of following hyperlinks. The element does not + represent any content beyond this information. + --> + + <!-- + BDO + html4: + The BDO element allows authors to turn off the bidirectional algorithm for + selected fragments of text. + + html5: + The bdo element represents explicit text directionality formatting control + for its children. It allows authors to override the Unicode bidirectional + algorithm by explicitly specifying a direction override. + --> + + <!-- + <li><p>The <code data-anolis-spec=html>blockquote</code> element now + represents a section that is quoted <em>from another source</em> (and that + is not necessarily "long"). + + html4: + These two elements designate quoted text. BLOCKQUOTE is for long + quotations (block-level content) + + html5: + The blockquote element represents a section that is quoted from another + source. + --> + + <!-- + BODY + html4: + The body of a document contains the document's content. + + html5: + The body element represents the main content of the document. + --> + + <!-- + BR + html4: + The BR element forcibly breaks (ends) the current line of text. + + html5: + The br element represents a line break. + --> + + <!-- + BUTTON + html4: + Buttons created with the BUTTON element function just like buttons created + with the INPUT element + html5: + The button element represents a button. + --> + + <!-- + CAPTION + html4: + When present, the CAPTION element's text should describe the nature of the + table. + + html5: + The caption element represents the title of the table that is its parent, + if it has a parent and that is a table element. + --> + <li><p>The <code data-anolis-spec=html>cite</code> element now solely represents the title of a work (e.g. a book, a paper, an essay, a poem, a score, a song, a script, a film, a TV show, a game, a sculpture, a @@ -724,41 +848,633 @@ where it is used to mark up the name of a person is no longer considered conforming.</p></li> + <!-- + CODE + html4: + Designates a fragment of computer code. + html5: + The code element represents a fragment of computer code. + --> + + <!-- + COL + html4: + The COL element allows authors to group together attribute specifications + for table columns. + + html5: + If a col element has a parent and that is a colgroup element that itself + has a parent that is a table element, then the col element represents one + or more columns in the column group represented by that colgroup. + --> + + <!-- + COLGROUP + html4: + The COLGROUP element creates an explicit column group. + + html5: + The colgroup element represents a group of one or more columns in the + table that is its parent, if it has a parent and that is a table element. + --> + + <!-- + DD + covered by dl + --> + + <!-- + DEL + html4: + INS and DEL are used to markup sections of the document that have been + inserted or deleted with respect to a different version of a document + + html5: + The del element represents a removal from the document. + --> + + <!-- + DFN + html4: + Indicates that this is the defining instance of the enclosed term. + + html5: + The dfn element represents the defining instance of a term. + --> + + <!-- + DIV + html4: + The DIV and SPAN elements, in conjunction with the id and class + attributes, offer a generic mechanism for adding structure to documents. + These elements define content to be inline (SPAN) or block-level (DIV) but + impose no other presentational idioms on the content. Thus, authors may + use these elements in conjunction with style sheets, the lang attribute, + etc., to tailor HTML to their own needs and tastes. + + html5: + The div element has no special meaning at all. It represents its children. + It can be used with the class, lang, and title attributes to mark up + semantics common to a group of consecutive elements. + --> + <li><p>The <code data-anolis-spec=html>dl</code> element now represents an association list of name-value groups, and is no longer said to be appropriate for dialogue.</p></li> + + <!-- + DT + covered by dl + --> + + <!-- + EM + html4: + Indicates emphasis. + + html5: + The em element represents stress emphasis of its contents. + --> + + <!-- + FIELDSET + html4: + The FIELDSET element allows authors to group thematically related controls + and labels. + + html5: + The fieldset element represents a set of form controls optionally grouped + under a common name. + --> + + <!-- + FORM + html4: + The FORM element acts as a container for controls. + + html5: + The form element represents a collection of form-associated elements, some of which can represent editable values that can be submitted to a server for processing. + --> + + <!-- + <li><p>The <code data-anolis-spec=html>h1</code>-<code + data-anolis-spec=html>h6</code> elements in HTML4 are said to have + different importance. In HTML5, they are said to have different <span + data-anolis-spec=html>ranks</span>, which affect the outline algorithm, + but do not affect importance. + + html4: + A heading element briefly describes the topic of the section it + introduces. Heading information may be used by user agents, for example, + to construct a table of contents for a document automatically. + + There are six levels of headings in HTML with H1 as the most important and + H6 as the least. Visual browsers usually render more important headings in + larger fonts than less important ones. + + html5: + These elements represent headings for their sections. + + The semantics and meaning of these elements are defined in the section on + headings and sections. + + These elements have a rank given by the number in their name. The h1 + element is said to have the highest rank, the h6 element has the lowest + rank, and two elements with the same name have equal rank. + + well, they intend the same semantics, basically. + --> + + <!-- + HEAD + html4: + The HEAD element contains information about the current document, such as + its title, keywords that may be useful to search engines, and other data + that is not considered document content. + + html5: + The head element represents a collection of metadata for the Document. + --> <li><p>The <code data-anolis-spec=html>hr</code> element now represents a paragraph-level thematic break. + + <!-- + HTML + html4: + After document type declaration, the remainder of an HTML document is + contained by the HTML element. + + html5: + The html element represents the root of an HTML document. + --> <li><p>The <code data-anolis-spec=html>i</code> element now represents a span of text in an alternate voice or mood, or otherwise offset from the normal prose in a manner indicating a different quality of text, such as a taxonomic designation, a technical term, an idiomatic phrase from another language, a thought, or a ship name in Western texts.</p></li> + + <!-- + IFRAME + html4: + The IFRAME element allows authors to insert a frame within a block of + text. Inserting an inline frame within a section of text is much like + inserting an object via the OBJECT element: they both allow you to insert + an HTML document in the middle of another, they may both be aligned with + surrounding text, etc. + + html5: + The iframe element represents a nested browsing context. + --> + + <!-- + IMG + html4: + The IMG element embeds an image in the current document at the location + of the element's definition. + + html5: + An img element represents an image. + --> + + <!-- + INPUT + + type html4 html5 + text Creates a single-line text input control. + Text with no line breaks; A text field. The + input element represents a one line plain text + edit control for the element's value. + password Like "text", but the input text is rendered in such a way as + to hide the characters + Text with no line breaks (sensitive + information); A text field that obscures data + entry. The input element represents a one line + plain text edit control for the element's + value. The user agent should obscure the value + so that people other than the user cannot see + it. + checkbox Checkboxes are on/off switches that may be toggled by the + user. + A set of zero or more values from a predefined + list; A checkbox. The input element represents + a two-state control that represents the + element's checkedness state. + radio Radio buttons are like checkboxes except that when several + share the same control name, they are mutually exclusive + An enumerated value; A radio button. The input + element represents a control that, when used in + conjunction with other input elements, forms a + radio button group in which only one control + can have its checkedness state set to true. + submit When activated, a submit button submits a form. A form may + contain more than one submit button. + An enumerated value, with the extra semantic + that it must be the last value selected and + initiates form submission; A button. The input + element represents a button that, when + activated, submits the form. + image Creates a graphical submit button. + A coordinate, relative to a particular image's + size, with the extra semantic that it must be + the last value selected and initiates form + submission; Either a clickable image, or a + button. The input element represents either an + image from which a user can select a coordinate + and submit the form, or alternatively a button + from which the user can submit the form. The + element is a button, specifically a submit + button. + reset When activated, a reset button resets all controls to their + initial values. + n/a; A button. The input element represents a + button that, when activated, resets the form. + button Push buttons have no default behavior. + n/a; A button. The input element represents a + button with no default behavior. + hidden Authors may create controls that are not rendered but whose + values are submitted with a form. Authors generally use this + control type to store information between client/server + exchanges that would otherwise be lost due to the stateless + nature of HTTP (see [RFC2616]). The INPUT element is used to + create a hidden control. + An arbitrary string; n/a. The input element + represents a value that is not intended to be + examined or manipulated by the user. + file This control type allows the user to select files so that + their contents may be submitted with a form. The INPUT + element is used to create a file select control. + Zero or more files each with a MIME type and + optionally a file name; A label and a button. + The input element represents a list of selected + files, each file consisting of a file name, a + file type, and a file body (the contents of the + file). + --> + + <!-- + INS + see DEL above + --> + + <!-- + KBD + html4: + Indicates text to be entered by the user. + + html5: + The kbd element represents user input (typically keyboard input, although + it may also be used to represent other input, such as voice commands). + --> <li><p>For the <code data-anolis-spec=html>label</code> element the browser should no longer move focus from the label to the control unless such behavior is standard for the underlying platform user interface.</p></li> - + + <!-- + LEGEND + html4: + The LEGEND element allows authors to assign a caption to a FIELDSET. + + html5: + The legend element represents a caption for the rest of the contents of + the legend element's parent fieldset element, if any. + --> + + <!-- + LI + html4: + Both types of lists are made up of sequences of list items defined by the + LI element + + html5: + The li element represents a list item. + --> + + <!-- + LINK + html4: + This element defines a link. + + html5: + The link element allows authors to link their document to other resources. + --> + + <!-- + MAP + html4: + The MAP element specifies a client-side image map (or other navigation + mechanism) + + html5: + The map element, in conjunction with any area element descendants, defines + an image map. The element represents its children. + --> + <li><p>The <code data-anolis-spec=html>menu</code> element is redefined to be useful for toolbars and context menus.</p></li> - + + <li><p>The <code data-anolis-spec=html>meta</code> element when it has a + <code data-anolis-spec=html title=attr-meta-http-equiv>http-equiv</code> + attribute, is no longer said to be used by HTTP servers to create HTTP + headers in the HTTP response. Instead, it is said to be a pragma directive + to be used by the user agent. + + <li><p>The <code data-anolis-spec=html>noscript</code> element is no + longer said to be rendered when the user agent doesn't support a scripting + language invoked by a <code data-anolis-spec=html>script</code> element + earlier in the document. + + <!-- + OBJECT + html4: + The OBJECT element allows authors to control whether data should be + rendered externally or by some program, specified by the author, that + renders the data within the user agent. + + html5: + The object element can represent an external resource, which, depending on + the type of the resource, will either be treated as an image, as a nested + browsing context, or as an external resource to be processed by a plugin. + --> + + <!-- + OL + html4: + Ordered and unordered lists are rendered in an identical manner except + that visual user agents number ordered list items. User agents may present + those numbers in a variety of ways. Unordered list items are not numbered. + + html5: + The ol element represents a list of items, where the items have been + intentionally ordered, such that changing the order would change the + meaning of the document. + --> + + <!-- + OPTGROUP + html4: + The OPTGROUP element allows authors to group choices logically. + + html5: + The optgroup element represents a group of option elements with a common + label. + --> + + <!-- + OPTION + html4: + Each choice offered by the menu is represented by an OPTION element. + + html5: + The option element represents an option in a select element ... + --> + + <!-- + P + html4: + The P element represents a paragraph. + + html5: + The p element represents a paragraph. + --> + + <!-- + PARAM + html4: + PARAM elements specify a set of values that may be required by an object + at run-time. + + html5: + The param element defines parameters for plugins invoked by object + elements. It does not represent anything on its own. + --> + + <!-- + PRE + html4: + The PRE element tells visual user agents that the enclosed text is + "preformatted". + + html5: + The pre element represents a block of preformatted text, in which + structure is represented by typographic conventions rather than by + elements. + --> + + <!-- + Q + html4: + These two elements designate quoted text. ... Q is intended for short + quotations (inline content) that don't require paragraph breaks. + + html5: + The q element represents some phrasing content quoted from another source. + --> + <li><p>The <code data-anolis-spec=html>s</code> element now represents contents that are no longer accurate or no longer relevant.</p></li> + + <!-- + SAMP + html4: + Designates sample output from programs, scripts, etc. + + html5: + The samp element represents (sample) output from a program or computing + system. + --> + + <li><p>The <code data-anolis-spec=html>script</code> element can now be + used for scripts or for custom data blocks. + + <!-- + SELECT + html4: + The SELECT element creates a menu. Menus offer users options from which + to choose. + + html5: + The select element represents a control for selecting amongst a set of + options. + --> <li><p>The <code data-anolis-spec=html>small</code> element now represents side comments such as small print.</p></li> + + <!-- + SPAN + html4: + The DIV and SPAN elements, in conjunction with the id and class + attributes, offer a generic mechanism for adding structure to documents. + These elements define content to be inline (SPAN) or block-level (DIV) but + impose no other presentational idioms on the content. Thus, authors may + use these elements in conjunction with style sheets, the lang attribute, + etc., to tailor HTML to their own needs and tastes. + + html5: + The span element doesn't mean anything on its own, but can be useful when + used together with the global attributes, e.g. class, lang, or dir. It + represents its children. + --> <li><p>The <code data-anolis-spec=html>strong</code> element now represents importance rather than strong emphasis.</p></li> - + + <!-- + STYLE + html4: + The STYLE element allows authors to put style sheet rules in the head of + the document. + + html5: + The style element allows authors to embed style information in their + documents. The style element is one of several inputs to the styling + processing model. The element does not represent content for the user. + --> + + <!-- + SUB and SUP + html4: + Many scripts (e.g., French) require superscripts or subscripts for proper + rendering. The SUB and SUP elements should be used to markup text in + these cases. + + html5: + The sup element represents a superscript and the sub element represents a + subscript. + --> + + <!-- + TABLE + html4: + The TABLE element contains all other elements that specify caption, rows, + content, and formatting. + + html5: + The table element represents data with more than one dimension, in the + form of a table. + --> + + <!-- + TBODY + html4: + The table body should contain rows of table data. + + html5: + The tbody element represents a block of rows that consist of a body of + data for the parent table element, if the tbody element has a parent and + it is a table. + --> + + <!-- + TD + html4: + The TD element defines a cell that contains data. + + html5: + The td element represents a data cell in a table. + --> + + <!-- + TEXTAREA + html4: + The TEXTAREA element creates a multi-line text input control. User + agents should use the contents of this element as the initial value of + the control and should render this text initially. + + html5: + The textarea element represents a multiline plain text edit control for + the element's raw value. The contents of the control represent the control's default value. + --> + + <!-- + TFOOT + html4: + The table head and table foot should contain information about the table's + columns. + + html5: + The tfoot element represents the block of rows that consist of the column + summaries (footers) for the parent table element, if the tfoot element has + a parent and it is a table. + --> + + <!-- + TH + html4: + The TH element defines a cell that contains header information. + + html5: + The th element represents a header cell in a table. + --> + + <!-- + THEAD + html4: + The table head and table foot should contain information about the table's columns. + + html5: + The thead element represents the block of rows that consist of the column + labels (headers) for the parent table element, if the thead element has a + parent and it is a table. + --> + + <!-- + TITLE + html4: + Authors should use the TITLE element to identify the contents of a + document. Since users often consult documents out of context, authors + should provide context-rich titles. + + html5: + The title element represents the document's title or name. Authors should + use titles that identify their documents even when they are used out of + context, for example in a user's history or bookmarks, or in search + results. + --> + + <!-- + TR + html4: + The TR elements acts as a container for a row of table cells. + + html5: + The tr element represents a row of cells in a table. + --> + <li><p>The <code data-anolis-spec=html>u</code> element now represents a span of text with an unarticulated, though explicitly rendered, non-textual annotation, such as labeling the text as being a proper name in Chinese text (a Chinese proper name mark), or labeling the text as being misspelt.</p></li> + + <!-- + UL + html4: + Ordered and unordered lists are rendered in an identical manner except + that visual user agents number ordered list items. User agents may present + those numbers in a variety of ways. Unordered list items are not numbered. + + html5: + The ul element represents a list of items, where the order of the items is + not important — that is, where changing the order would not materially + change the meaning of the document. + --> + + <!-- + VAR + html4: + Indicates an instance of a variable or program argument. + + html5: + The var element represents a variable. This could be an actual variable in + a mathematical expression or programming context, an identifier + representing a constant, a function parameter, or just be a term used as a + placeholder in prose. + --> </ul> @@ -1080,6 +1796,10 @@ <p>The <code data-anolis-spec=html>table</code> element now allows the <code data-anolis-spec=html>tfoot</code> element to be the last child. + + <p>The <code data-anolis-spec=html>caption</code> element now allows flow + content, but with no descendant <code data-anolis-spec=html>table</code> + elements. <p>The <code data-anolis-spec=html>th</code> element now allows flow content, but with no <code data-anolis-spec=html>header</code>, <code @@ -1193,28 +1913,28 @@ <p>WHATWG HTML has further APIs that are not in HTML5 but are separate specifications at the W3C: <ul> - <li>An API for microdata. - - <li>An API for immediate-mode bitmap graphics (the <code - data-anolis-spec=html title=canvas-context-2d>2d</code> context for the - <code data-anolis-spec=html>canvas</code> element). + <li>An API for microdata. + + <li>An API for immediate-mode bitmap graphics (the <code + data-anolis-spec=html title=canvas-context-2d>2d</code> context for the + <code data-anolis-spec=html>canvas</code> element). - <li>An API for cross-document messaging and channel messaging (<code - data-anolis-spec=html title=dom-window-postMessage>postMessage()</code> - and <code data-anolis-spec=html>MessageChannel</code>). + <li>An API for cross-document messaging and channel messaging (<code + data-anolis-spec=html title=dom-window-postMessage>postMessage()</code> + and <code data-anolis-spec=html>MessageChannel</code>). - <li>An API for runnings scripts in the background (<code - data-anolis-spec=html>Worker</code> and <code - data-anolis-spec=html>SharedWorker</code>). + <li>An API for runnings scripts in the background (<code + data-anolis-spec=html>Worker</code> and <code + data-anolis-spec=html>SharedWorker</code>). - <li>An API for client-side storage (<code data-anolis-spec=html - title=dom-localStorage>localStorage</code> and <code data-anolis-spec=html - title=dom-sessionStorage>sessionStorage</code>). + <li>An API for client-side storage (<code data-anolis-spec=html + title=dom-localStorage>localStorage</code> and <code data-anolis-spec=html + title=dom-sessionStorage>sessionStorage</code>). - <li>An API for bidirectional client-server communication (<code - data-anolis-spec=html>WebSocket</code>). + <li>An API for bidirectional client-server communication (<code + data-anolis-spec=html>WebSocket</code>). - <li>An API for server-to-client data push (<code data-anolis-spec=html>EventSource</code>). + <li>An API for server-to-client data push (<code data-anolis-spec=html>EventSource</code>). </ul> <h3 id="document-extensions">Extensions to
Received on Monday, 5 March 2012 09:54:21 UTC