W3C home > Mailing lists > Public > public-html-commits@w3.org > January 2009

html5/html4-differences Overview.html,1.54,1.55 Overview.src.html,1.33,1.34

From: Anne van Kesteren via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 26 Jan 2009 12:22:00 +0000
To: public-html-commits@w3.org
Message-Id: <E1LRQTZ-0008Lq-01@lionel-hutz.w3.org>

Update of /sources/public/html5/html4-differences
In directory hutz:/tmp/cvs-serv32063

Modified Files:
	Overview.html Overview.src.html 
Log Message:
address comments from simonp; all but the pony, that is

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/html4-differences/Overview.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -d -r1.54 -r1.55
--- Overview.html	23 Jan 2009 18:21:51 -0000	1.54
+++ Overview.html	26 Jan 2009 12:21:58 -0000	1.55
@@ -20,13 +20,13 @@
 
    <h1 id=html5-diff>HTML&nbsp;5 differences from HTML&nbsp;4</h1>
 
-   <h2 class="no-num no-toc" id=w3c-doctype>Editor's Draft 23 January 2009</h2>
+   <h2 class="no-num no-toc" id=w3c-doctype>Editor's Draft 26 January 2009</h2>
 
    <dl>
     <dt>This Version:
 
     <dd><a
-     href="http://www.w3.org/TR/2009/ED-html5-diff-20090123/">http://www.w3.org/TR/2009/ED-html5-diff-20090123/</a>
+     href="http://www.w3.org/TR/2009/ED-html5-diff-20090126/">http://www.w3.org/TR/2009/ED-html5-diff-20090126/</a>
 
     <dt>Latest Version:
 
@@ -304,7 +304,7 @@
     <li>The focus on defining the semantics in detail (e.g. the outline
      algorithm, replacing the vague semantics in HTML&nbsp;4).
 
-    <li>The server-sent events feature (the <code>event-source</code>
+    <li>The server-sent events feature (the <code>eventsource</code>
      element).
 
     <li>The <code>datagrid</code> element.
@@ -345,8 +345,8 @@
   <p>The HTML&nbsp;5 language has a "custom" HTML syntax that is compatible
    with HTML&nbsp;4 and XHTML&nbsp;1 documents published on the Web, but is
    not compatible with the more esoteric SGML features of HTML&nbsp;4, such
-   as <code>&lt;em/content/</code>. Documents using the HTML syntax must be
-   served with the <code>text/html</code> media type.
+   as the NET syntax (i.e. <code>&lt;em/content/</code>). Documents using the
+   HTML syntax must be served with the <code>text/html</code> media type.
 
   <p>HTML&nbsp;5 also defines detailed parsing rules (including "error
    handling") for this syntax which are largely compatible with popular
@@ -399,11 +399,11 @@
     file. This character provides a signature for the encoding used.
 
    <li>Using a <code>meta</code> element with a <code>charset</code>
-    attribute that specifies the encoding as the first element child of the
-    <code>head</code> element. <code>&lt;meta charset="UTF-8"></code> could
-    be used to specify the UTF-8 encoding. This replaces the need for
-    <code>&lt;meta http-equiv="Content-Type" content="text/html;
-    charset=UTF-8"></code>
+    attribute that specifies the encoding within the first 512 bytes of the
+    document. E.g. <code>&lt;meta charset="UTF-8"></code> could be used to
+    specify the UTF-8 encoding. This replaces the need for <code>&lt;meta
+    http-equiv="Content-Type" content="text/html; charset=UTF-8"></code>
+    although that syntax is still allowed.
   </ul>
 
   <p>For the XML syntax authors have to use the rules as set forth in the XML
@@ -422,7 +422,7 @@
   <p>The <code title="">DOCTYPE</code> declaration is <code>&lt;!DOCTYPE
    html></code> and is case-insensitive in the HTML syntax. <code
    title="">DOCTYPE</code>s from earlier versions of HTML were longer because
-   the HTML language was SGML based and therefore required a reference to a
+   the HTML language was SGML-based and therefore required a reference to a
    DTD. With HTML&nbsp;5 this is no longer the case and the <code
    title="">DOCTYPE</code> is only needed to enable standards mode for
    documents written using the HTML syntax. Browsers already do this for
@@ -524,6 +524,10 @@
     <p><code>meter</code> represents a measurement, such as disk usage.
 
    <li>
+    <p><code>progress</code> represents a completion of a task, such as
+     downloading or when performing a series of expensive operations.
+
+   <li>
     <p><code>time</code> represents a date and/or time.
 
    <li>
@@ -566,10 +570,6 @@
      calculation done through scripting.
 
    <li>
-    <p><code>progress</code> represents a completion of a task, such as
-     downloading or when performing a series of expensive operations.
-
-   <li>
     <p><code>ruby</code>, <code>rt</code> and <code>rb</code> allow for
      marking up ruby annotations.
   </ul>
@@ -668,13 +668,6 @@
      descendant of).
 
    <li>
-    <p>The <code>form</code> and <code>select</code> elements (as well as the
-     <code>datalist</code> element) have a <code>data</code> attribute that
-     allows for automatically prefilling of form controls, in case of
-     <code>form</code>, or the form control, in case of <code>select</code>
-     and <code>datalist</code>, with data from the server.
-
-   <li>
     <p>The new <code>required</code> attribute applies to <code>input</code>
      (except when the <code>type</code> attribute is <code>hidden</code>,
      <code>image</code> or some button type such as <code>submit</code>) and
@@ -682,8 +675,8 @@
      in order to submit the form.
 
    <li>
-    <p>You can now disable an entire <code>fieldset</code> by using the
-     <code>disabled</code> attribute on it. This was not possible before.
+    <p>The <code>fieldset</code> element now allows the <code>disabled</code>
+     attribute disabling all its contents when specified.
 
    <li>
     <p>The <code>input</code> element has several new attributes to specify
@@ -758,7 +751,7 @@
    <li>The <code>hidden</code> attribute indicates that an element is not
     yet, or is no longer, relevant.
 
-   <li>The <code>data-<var>*</var></code> collection of author defined
+   <li>The <code>data-<var>*</var></code> collection of author-defined
     attributes. Authors can define any attribute they want as long as they
     prefix it with <code>data-</code> to avoid clashes with future versions
     of HTML. The only requirement on these attributes is that they are not
@@ -989,8 +982,7 @@
 
    <li><code>scrolling</code> attribute on <code>iframe</code>.
 
-   <li><code>size</code> attribute on <code>hr</code>, <code>input</code> and
-    <code>select</code>.
+   <li><code>size</code> attribute on <code>hr</code>.
 
    <li><code>type</code> attribute on <code>li</code>, <code>ol</code> and
     <code>ul</code>.
@@ -1139,8 +1131,8 @@
     clarifying what happens when NaN and Infinity are passed and fixing the
     definitions of <code>arc()</code> and <code>arcTo()</code>.
 
-   <li><code>innerHTML</code> in XML was slightly changed to improve round
-    tripping.
+   <li><code>innerHTML</code> in XML was slightly changed to improve
+    round-tripping.
 
    <li>The <code>toDataURL()</code> method on the <code>canvas</code> element
     now supports setting a quality level when the media type argument is
@@ -1226,8 +1218,8 @@
    <li>The <code>top</code> attribute of the <code>Window</code> object is
     now defined.
 
-   <li>The <code>a</code> element now allows nested flow content, e.g. a
-    <code>div</code> element, but not itself.
+   <li>The <code>a</code> element now allows nested flow content, but not
+    nested interactive content.
 
    <li>It is now defined what the <code>header</code> element means to
     document summaries and table of contents.
@@ -1272,15 +1264,7 @@
    <li>An alternative syntax for the <code title="">DOCTYPE</code> is allowed
     for compatibility with XSLT.
 
-   <li>Web Forms 2.0 has been fully integrated into the specification. This
-    means that just like in HTML&nbsp;4 there is a chapter on forms.
-
-   <li>Features from Web Forms 2.0 that did not make the cut: repetition
-    templates, XML submission, the <code>replace</code> attribute, the
-    <code>inputmode</code> attribute and seeding of values through an
-    external resource.
-
-   <li>Data templates have been removed as well (consisted of the
+   <li>Data templates have been removed (consisted of the
     <code>datatemplate</code>, <code>rule</code> and <code>nest</code>
     elements).
 
@@ -1296,26 +1280,9 @@
    <li>The <code>totalBytes</code> and <code>bufferedBytes</code> attributes
     have been removed from the media elements.
 
-   <li>The <code>input</code> element gained a <code>placeholder</code>
-    attribute.
-
    <li>The <code>Location</code> object gained a <code>resolveURL()</code>
     method.
 
-   <li><code>object</code> elements now partake in form submission.
-
-   <li>The <code>type</code> attribute of the <code>input</code> element
-    gained the values <code>color</code> and <code>search</code>.
-
-   <li>The <code>input</code> element gained a <code>multiple</code>
-    attribute which allows for either multiple e-mails or multiple files to
-    be uploaded depending on the value of the <code>type</code> attribute.
-
-   <li>The <code>input</code>, <code>button</code> and <code>form</code>
-    elements now have a <code>novalidate</code> attribute to indicate that
-    the form fields should not be required to have valid values upon
-    submission.
-
    <li>The <code>q</code> element has changed again. Punctation is to be
     provided by the user agent again.
 
@@ -1329,8 +1296,9 @@
     with the upcoming Web IDL specification.
 
    <li>Table headers can now have headers. User agents are required to
-    support a <code>headers</code> attribute pointing to a <code>td</code>
-    element, but authors are required to use <code>th</code> instead.
+    support a <code>headers</code> attribute pointing to a <code>td</code> or
+    <code>th</code> element, but authors are required to only let them point
+    to <code>th</code> elements.
 
    <li>Interested parties can now register new <code>http-equiv</code>
     values.
@@ -1344,13 +1312,6 @@
    <li>It is now defined how HTML is to be used within the SVG
     <code>foreignObject</code> element.
 
-   <li>When the <code>label</code> element contains an <code>input</code> it
-    may still have a <code>for</code> attribute as long as it points to the
-    <code>input</code> element it contains.
-
-   <li>The <code>input</code> element now has an <code>indeterminate</code>
-    DOM attribute.
-
    <li>The notification API has been dropped.
 
    <li>How [[Get]] works for the <code>HTMLDocument</code> and
@@ -1365,6 +1326,75 @@
     updated.
   </ul>
 
+  <p>Web Forms 2.0, previously a standalone specification, has been fully
+   integrated into HTML&nbsp;5 since last publication. The following changes
+   were made to the forms chapter:
+
+  <ul>
+   <li>Support for XML submission has been removed.
+
+   <li>Support for form filling has been removed.
+
+   <li>Support for filling of the <code>select</code> and
+    <code>datalist</code> elements through the <code>data</code> attribute
+    has been removed.
+
+   <li>Support for associating a field with multiple forms has been removed.
+    A field can still be associated with a form it is not nested in through
+    the <code>form</code> attribute.
+
+   <li>The <code>dispatchFormInput()</code> and
+    <code>dispatchFormChange()</code> methods have been removed.
+
+   <li>Repetition templates have been removed.
+
+   <li>The <code>inputmode</code> attribute has been removed.
+
+   <li>The <code>input</code> element in the File Upload state no longer
+    supports the <code>min</code> and <code>max</code> attributes.
+
+   <li>The <code>allow</code> attribute on <code>input</code> elements in the
+    File Upload state is no longer authorative.
+
+   <li>The <code>pattern</code> and <code>accept</code> attributes for
+    <code>textarea</code> have been removed.
+
+   <li>RFC 3106 is no longer explicitly supported.
+
+   <li>The <code>submit()</code> method now just submits, it no longer
+    ensures the form controls are valid.
+
+   <li>The <code>input</code> element in the Range state now defaults to the
+    middle, rather than the minimum value.
+
+   <li>The <code>size</code> attribute on the <code>input</code> element is
+    now conforming (rather than deprecated).
+
+   <li><code>object</code> elements now partake in form submission.
+
+   <li>The <code>type</code> attribute of the <code>input</code> element
+    gained the values <code>color</code> and <code>search</code>.
+
+   <li>The <code>input</code> element gained a <code>multiple</code>
+    attribute which allows for either multiple e-mails or multiple files to
+    be uploaded depending on the value of the <code>type</code> attribute.
+
+   <li>The <code>input</code>, <code>button</code> and <code>form</code>
+    elements now have a <code>novalidate</code> attribute to indicate that
+    the form fields should not be required to have valid values upon
+    submission.
+
+   <li>When the <code>label</code> element contains an <code>input</code> it
+    may still have a <code>for</code> attribute as long as it points to the
+    <code>input</code> element it contains.
+
+   <li>The <code>input</code> element now has an <code>indeterminate</code>
+    DOM attribute.
+
+   <li>The <code>input</code> element gained a <code>placeholder</code>
+    attribute.
+  </ul>
+
   <h3 id=changes-2008-01-22><span class=secno>5.2 </span>Changes from 22
    January 2008 to 10 June 2008</h3>
 
@@ -1513,8 +1543,8 @@
    <dt>[<dfn id=ref-xml>XML</dfn>]
 
    <dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup Language
-    (XML) 1.0 (Fourth Edition)</a></cite>, T. Bray, J. Paoli, C.
-    Sperberg-McQueen, E. Maler, F. Yergeau, editors. W3C, September 2006.
+    (XML) 1.0 (Fifth Edition)</a></cite>, T. Bray, J. Paoli, C.
+    Sperberg-McQueen, E. Maler, F. Yergeau, editors. W3C, November 2008.
 
    <dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in XML 1.0
     (Second Edition)</a></cite>, T. Bray, D. Hollander, A. Layman, R. Tobin,

Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/html4-differences/Overview.src.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -d -r1.33 -r1.34
--- Overview.src.html	23 Jan 2009 18:21:51 -0000	1.33
+++ Overview.src.html	26 Jan 2009 12:21:58 -0000	1.34
@@ -225,7 +225,7 @@
      <li>The focus on defining the semantics in detail (e.g. the outline
      algorithm, replacing the vague semantics in HTML&nbsp;4).</li>
 
-     <li>The server-sent events feature (the <code>event-source</code>
+     <li>The server-sent events feature (the <code>eventsource</code>
      element).</li>
 
      <li>The <code>datagrid</code> element.</li>
@@ -267,9 +267,9 @@
     <p>The HTML&nbsp;5 language has a "custom" HTML syntax that is
     compatible with HTML&nbsp;4 and XHTML&nbsp;1 documents published on the
     Web, but is not compatible with the more esoteric SGML features of
-    HTML&nbsp;4, such as <code>&lt;em/content/</code>. Documents using the
-    HTML syntax must be served with the <code>text/html</code> media
-    type.</p>
+    HTML&nbsp;4, such as the NET syntax (i.e. <code>&lt;em/content/</code>).
+    Documents using the HTML syntax must be served with the
+    <code>text/html</code> media type.</p>
 
     <p>HTML&nbsp;5 also defines detailed parsing rules (including "error
     handling") for this syntax which are largely compatible with popular
@@ -311,9 +311,9 @@
     
     <h3 id="character-encoding">Character Encoding</h3>
     
-    <p>For the HTML syntax of HTML&nbsp;5 authors have three means of setting
-    the character encoding:</p>
-    
+    <p>For the HTML syntax of HTML&nbsp;5 authors have three means of
+    setting the character encoding:</p>
+
     <ul>
       <li>At the transport level. By using the HTTP <code>Content-Type</code>
       header for instance.</li>
@@ -323,11 +323,12 @@
       used.</li>
 
       <li>Using a <code>meta</code> element with a <code>charset</code>
-      attribute that specifies the encoding as the first element child of
-      the <code>head</code> element. <code>&lt;meta charset="UTF-8"></code>
+      attribute that specifies the encoding within the first 512 bytes of
+      the document. E.g. <code>&lt;meta charset="UTF-8"></code>
       could be used to specify the UTF-8 encoding. This replaces the need
       for
-      <code>&lt;meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></code></li>
+      <code>&lt;meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></code>
+      although that syntax is still allowed.</li>
     </ul>
 
     <p>For the XML syntax authors have to use the rules as set forth in the
@@ -345,7 +346,7 @@
     <p>The <code title="">DOCTYPE</code> declaration is
     <code>&lt;!DOCTYPE html></code> and is case-insensitive in the HTML
     syntax. <code title="">DOCTYPE</code>s from earlier versions of HTML
-    were longer because the HTML language was SGML based and therefore
+    were longer because the HTML language was SGML-based and therefore
     required a reference to a DTD. With HTML&nbsp;5 this is no longer the
     case and the <code title="">DOCTYPE</code> is only needed to enable
     standards mode for documents written using the HTML syntax. Browsers
@@ -446,7 +447,10 @@
       
       <li><p><code>meter</code> represents a measurement, such as disk
       usage.</p></li>
-      
+
+      <li><p><code>progress</code> represents a completion of a task, such as
+      downloading or when performing a series of expensive operations.</p></li>
+
       <li><p><code>time</code> represents a date and/or time.</p></li>
       
       <li><p><code>canvas</code> is used for rendering dynamic bitmap graphics
@@ -484,9 +488,6 @@
       <li><p><code>output</code> represents some type of output, such as
       from a calculation done through scripting.</p></li>
 
-      <li><p><code>progress</code> represents a completion of a task, such as
-      downloading or when performing a series of expensive operations.</p></li>
-
       <li><p><code>ruby</code>, <code>rt</code> and <code>rb</code> allow
       for marking up ruby annotations.</p></li>
     </ul>
@@ -578,20 +579,15 @@
       controls to be associated with a form (e.g. one they are not a
       descendant of).
 
-      <li><p>The <code>form</code> and <code>select</code> elements (as well as
-      the <code>datalist</code> element) have a <code>data</code> attribute that
-      allows for automatically prefilling of form controls, in case of
-      <code>form</code>, or the form control, in case of <code>select</code> and
-      <code>datalist</code>, with data from the server.
-
       <li><p>The new <code>required</code> attribute applies to
       <code>input</code> (except when the <code>type</code> attribute is
       <code>hidden</code>, <code>image</code> or some button type such as
       <code>submit</code>) and <code>textarea</code>. It indicates that the user
       has to fill in a value in order to submit the form.
 
-      <li><p>You can now disable an entire <code>fieldset</code> by using the
-      <code>disabled</code> attribute on it. This was not possible before.
+      <li><p>The <code>fieldset</code> element now allows the
+      <code>disabled</code> attribute disabling all its contents when
+      specified.
 
       <li><p>The <code>input</code> element has several new attributes to
       specify constraints: <code>autocomplete</code>, <code>min</code>,
@@ -657,7 +653,7 @@
       <li>The <code>hidden</code> attribute indicates that an element is not
       yet, or is no longer, relevant.
 
-      <li>The <code>data-<var>*</var></code> collection of author defined
+      <li>The <code>data-<var>*</var></code> collection of author-defined
       attributes. Authors can define any attribute they want as long as they
       prefix it with <code>data-</code> to avoid clashes with future
       versions of HTML. The only requirement on these attributes is that
@@ -885,8 +881,7 @@
       
       <li><code>scrolling</code> attribute on <code>iframe</code>.
       
-      <li><code>size</code> attribute on <code>hr</code>, <code>input</code> and
-      <code>select</code>.
+      <li><code>size</code> attribute on <code>hr</code>.
       
       <li><code>type</code> attribute on <code>li</code>, <code>ol</code> and
       <code>ul</code>.
@@ -1027,8 +1022,8 @@
      been made in response to implementation and author feedback. E.g.
      clarifying what happens when NaN and Infinity are passed and fixing the
      definitions of <code>arc()</code> and <code>arcTo()</code>.</li>
-     <li><code>innerHTML</code> in XML was slightly changed to improve round
-     tripping.</li>
+     <li><code>innerHTML</code> in XML was slightly changed to improve
+     round-tripping.</li>
      <li>The <code>toDataURL()</code> method on the <code>canvas</code>
      element now supports setting a quality level when the media type
      argument is <code>image/jpeg</code>.</li>
@@ -1088,8 +1083,8 @@
      <code>target="_blank"</code> and <code>rel="noreferrer"</code>.</li>
      <li>The <code>top</code> attribute of the <code>Window</code> object is
      now defined.</li>
-     <li>The <code>a</code> element now allows nested flow content, e.g. a
-     <code>div</code> element, but not itself.</li>
+     <li>The <code>a</code> element now allows nested flow content, but not
+     nested interactive content.</li>
      <li>It is now defined what the <code>header</code> element means to
      document summaries and table of contents.</li>
      <li>What it means to fetch a resource is now defined.</li>
@@ -1120,14 +1115,7 @@
      reasons.</li>
      <li>An alternative syntax for the <code title="">DOCTYPE</code> is
      allowed for compatibility with XSLT.</li>
-     <li>Web Forms 2.0 has been fully integrated into the
-     specification. This means that just like in HTML&nbsp;4 there is a
-     chapter on forms.</li>
-     <li>Features from Web Forms 2.0 that did not make the cut: repetition
-     templates, XML submission, the <code>replace</code> attribute, the
-     <code>inputmode</code> attribute and
-     seeding of values through an external resource.</li>
-     <li>Data templates have been removed as well (consisted of the
+     <li>Data templates have been removed (consisted of the
      <code>datatemplate</code>, <code>rule</code> and <code>nest</code>
      elements).</li>
      <li>The media elements now support just a single <code>loop</code>
@@ -1138,21 +1126,8 @@
      the media elements.</li>
      <li>The <code>totalBytes</code> and <code>bufferedBytes</code>
      attributes have been removed from the media elements.</li>
-     <li>The <code>input</code> element gained a <code>placeholder</code>
-     attribute.</li>
      <li>The <code>Location</code> object gained a
      <code>resolveURL()</code> method.</li>
-     <li><code>object</code> elements now partake in form submission.</li>
-     <li>The <code>type</code> attribute of the <code>input</code> element
-     gained the values <code>color</code> and <code>search</code>.</li>
-     <li>The <code>input</code> element gained a <code>multiple</code>
-     attribute which allows for either multiple e-mails or multiple files to
-     be uploaded depending on the value of the <code>type</code>
-     attribute.</li>
-     <li>The <code>input</code>, <code>button</code> and <code>form</code>
-     elements now have a <code>novalidate</code> attribute to indicate that
-     the form fields should not be required to have valid values upon
-     submission.</li>
      <li>The <code>q</code> element has changed again. Punctation is to be
      provided by the user agent again.</li>
      <li>Various changes were made to the HTML parser algorithm to be more
@@ -1163,7 +1138,8 @@
      line with the upcoming Web IDL specification.</li>
      <li>Table headers can now have headers. User agents are required to
      support a <code>headers</code> attribute pointing to a <code>td</code>
-     element, but authors are required to use <code>th</code> instead.</li>
+     or <code>th</code> element, but authors are required to only let them
+     point to <code>th</code> elements.</li>
      <li>Interested parties can now register new <code>http-equiv</code>
      values.</li>
      <li>When the <code>meta</code> element has a <code>charset</code>
@@ -1172,11 +1148,6 @@
      <code>storageArea</code> attribute.</li>
      <li>It is now defined how HTML is to be used within the SVG
      <code>foreignObject</code> element.</li>
-     <li>When the <code>label</code> element contains an <code>input</code>
-     it may still have a <code>for</code> attribute as long as it points to
-     the <code>input</code> element it contains.</li>
-     <li>The <code>input</code> element now has an
-     <code>indeterminate</code> DOM attribute.</li>
      <li>The notification API has been dropped.</li>
      <li>How [[Get]] works for the <code>HTMLDocument</code> and
      <code>Window</code> objects is now defined.</li>
@@ -1189,6 +1160,57 @@
      updated.</li>
     </ul>
 
+    <p>Web Forms 2.0, previously a standalone specification, has been fully
+    integrated into HTML&nbsp;5 since last publication. The following
+    changes were made to the forms chapter:</p>
+
+    <ul>
+     <li>Support for XML submission has been removed.</li>
+     <li>Support for form filling has been removed.</li>
+     <li>Support for filling of the <code>select</code> and
+     <code>datalist</code> elements through the <code>data</code> attribute
+     has been removed.</li>
+     <li>Support for associating a field with multiple forms has been
+     removed. A field can still be associated with a form it is not nested
+     in through the <code>form</code> attribute.</li>
+     <li>The <code>dispatchFormInput()</code> and
+     <code>dispatchFormChange()</code> methods have been removed.</li>
+     <li>Repetition templates have been removed.</li>
+     <li>The <code>inputmode</code> attribute has been removed.</li>
+     <li>The <code>input</code> element in the File Upload state no longer
+     supports the <code>min</code> and <code>max</code> attributes.</li>
+     <li>The <code>allow</code> attribute on <code>input</code> elements in
+     the File Upload state is no longer authorative.</li>
+     <li>The <code>pattern</code> and <code>accept</code> attributes for
+     <code>textarea</code> have been removed.</li>
+     <li>RFC 3106 is no longer explicitly supported.</li>
+     <li>The <code>submit()</code> method now just submits, it no longer
+     ensures the form controls are valid.</li>
+     <li>The <code>input</code> element in the Range state now defaults to
+     the middle, rather than the minimum value.</li>
+     <li>The <code>size</code> attribute on the <code>input</code> element
+     is now conforming (rather than deprecated).</li>
+     <li><code>object</code> elements now partake in form submission.</li>
+     <li>The <code>type</code> attribute of the <code>input</code> element
+     gained the values <code>color</code> and <code>search</code>.</li>
+     <li>The <code>input</code> element gained a <code>multiple</code>
+     attribute which allows for either multiple e-mails or multiple files to
+     be uploaded depending on the value of the <code>type</code>
+     attribute.</li>
+     <li>The <code>input</code>, <code>button</code> and <code>form</code>
+     elements now have a <code>novalidate</code> attribute to indicate that
+     the form fields should not be required to have valid values upon
+     submission.</li>
+     <li>When the <code>label</code> element contains an <code>input</code>
+     it may still have a <code>for</code> attribute as long as it points to
+     the <code>input</code> element it contains.</li>
+     <li>The <code>input</code> element now has an
+     <code>indeterminate</code> DOM attribute.</li>
+     <li>The <code>input</code> element gained a <code>placeholder</code>
+     attribute.</li>
+    </ul>
+
+
     <h3 id="changes-2008-01-22">Changes from 22 January 2008 to 10 June 2008</h3>
 
     <ul>
@@ -1326,8 +1348,8 @@
       <dt>[<dfn id="ref-xml">XML</dfn>]</dt>
 
       <dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup Language
-      (XML) 1.0 (Fourth Edition)</a></cite>, T. Bray, J. Paoli, C.
-      Sperberg-McQueen, E. Maler, F. Yergeau, editors. W3C, September 2006.</dd>
+      (XML) 1.0 (Fifth Edition)</a></cite>, T. Bray, J. Paoli, C.
+      Sperberg-McQueen, E. Maler, F. Yergeau, editors. W3C, November 2008.</dd>
 
       <dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in XML 1.0
       (Second Edition)</a></cite>, T. Bray, D. Hollander, A. Layman, R. Tobin,
Received on Monday, 26 January 2009 12:22:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 26 January 2009 12:22:17 GMT