W3C home > Mailing lists > Public > public-html-commits@w3.org > September 2012

html5/spec acknowledgements.html,1.1274,1.1275 browsers.html,1.1257,1.1258 commands.html,1.221,1.222 constraints.html,1.171,1.172 dom.html,1.1250,1.1251 elements.html,1.245,1.246 global-attributes.html,1.171,1.172 history.html,1.1262,1.1263 index.html,1.1288,1.1289 interactions-with-xpath-and-xslt.html,1.93,1.94 single-page.html,1.94,1.95 spec.html,1.1965,1.1966 the-end.html,1.165,1.166 the-meta-element.html,1.171,1.172 the-script-element.html,1.170,1.171 urls.html,1.232,1.233 webappapis.html,1.375,1.376

From: Sam Ruby via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 07 Sep 2012 11:14:09 +0000
To: public-html-commits@w3.org
Message-Id: <E1T9wVl-00027F-Sy@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv8117

Modified Files:
	acknowledgements.html browsers.html commands.html 
	constraints.html dom.html elements.html global-attributes.html 
	history.html index.html interactions-with-xpath-and-xslt.html 
	single-page.html spec.html the-end.html the-meta-element.html 
	the-script-element.html urls.html webappapis.html 
Log Message:
commit 2f3bf2649f843063aed57c0bcf98c9d5cfbba685
Author: ianh <ianh@340c8d12-0b0e-0410-8428-c7bf67bfef74>
Date:   Thu Jul 12 19:25:06 2012 +0000

    [e] (0) fix contributor's name
    Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17752
    Affected topics: HTML
    
    git-svn-id: http://svn.whatwg.org/webapps@7176 340c8d12-0b0e-0410-8428-c7bf67bfef74
    (cherry picked from commit cadbeb6a77d5680767b803689adc6572f242df29)


Index: interactions-with-xpath-and-xslt.html
===================================================================
RCS file: /sources/public/html5/spec/interactions-with-xpath-and-xslt.html,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -d -r1.93 -r1.94
--- interactions-with-xpath-and-xslt.html	7 Sep 2012 00:13:58 -0000	1.93
+++ interactions-with-xpath-and-xslt.html	7 Sep 2012 11:14:06 -0000	1.94
@@ -424,9 +424,25 @@
   unaffected.) <a href="references.html#refsXSLT10">[XSLT10]</a></p> <!-- note:
   version matters for this ref -->
 
-  <p class="note">There are also additional comments regarding the
-  interaction of XSLT and HTML <a href="the-script-element.html#scriptTagXSLT">in the
-  <code>script</code> element section</a>.</p>
+  <hr><p>This specification does not specify precisely how XSLT processing
+  interacts with the <a href="parsing.html#html-parser">HTML parser</a> infrastructure (for
+  example, whether an XSLT processor acts as if it puts any elements
+  into a <a href="parsing.html#stack-of-open-elements">stack of open elements</a>). However, XSLT
+  processors must <a href="the-end.html#stop-parsing">stop parsing</a> if they successfully
+  complete, and must set the <a href="dom.html#current-document-readiness">current document readiness</a>
+  first to "<code title="">interactive</code>"<!-- this synchronously
+  fires an event --> and then to "<code title="">complete</code>"<!--
+  this also synchronously fires an event --> if they are aborted.</p>
+
+  <hr><p>This specification does not specify how XSLT interacts with the
+  <a href="history.html#navigate" title="navigate">navigation</a> algorithm, how it fits in
+  with the <a href="webappapis.html#event-loop">event loop</a>, nor how error pages are to be
+  handled (e.g. whether XSLT errors are to replace an incremental XSLT
+  output, or are rendered inline, etc).</p>
+
+  <p class="note">There are also additional non-normative comments
+  regarding the interaction of XSLT and HTML <a href="the-script-element.html#scriptTagXSLT">in the <code>script</code> element
+  section</a>.</p>
 
   </div>
 

Index: dom.html
===================================================================
RCS file: /sources/public/html5/spec/dom.html,v
retrieving revision 1.1250
retrieving revision 1.1251
diff -u -d -r1.1250 -r1.1251
--- dom.html	7 Sep 2012 00:13:57 -0000	1.1250
+++ dom.html	7 Sep 2012 11:14:05 -0000	1.1251
@@ -343,18 +343,21 @@
   <code><a href="#document">Document</a></code> object. <a href="references.html#refsDOMCORE">[DOMCORE]</a></p>
 
   <p><dfn id="the-document's-address">The document's address</dfn> is an <a href="urls.html#absolute-url">absolute URL</a>
-  that is set when the <code><a href="#document">Document</a></code> is created. <dfn id="the-document's-current-address">The
-  document's current address</dfn> is an <a href="urls.html#absolute-url">absolute URL</a>
+  that is initially set when the <code><a href="#document">Document</a></code> is created but
   that can change during the lifetime of the <code><a href="#document">Document</a></code>,
   for example when the user <a href="history.html#navigate" title="navigate">navigates</a> to
   a <a href="history.html#scroll-to-fragid" title="navigate-fragid">fragment identifier</a> on the
   page or when the <code title="dom-history-pushState"><a href="history.html#dom-history-pushstate">pushState()</a></code> method is called
-  with a new <a href="urls.html#url">URL</a>. <span class="impl"><a href="#the-document's-current-address">The document's
-  current address</a> must be set to <a href="#the-document's-address">the document's
-  address</a> when the <code><a href="#document">Document</a></code> is created.</span></p>
+  with a new <a href="urls.html#url">URL</a>.</p>
+  <!--
+    http://www.hixie.ch/tests/adhoc/dom/level0/history/pushState/002/
+    http://www.hixie.ch/tests/adhoc/html/navigation/fragids/016.html
+  -->
 
-  <p class="note">Interactive user agents typically expose <a href="#the-document's-current-address">the
-  document's current address</a> in their user interface.</p>
+  <p class="warning">Interactive user agents typically expose
+  <a href="#the-document's-address">the document's address</a> in their user interface. This is
+  the primary mechanism by which a user can tell if a site is
+  attempting to impersonate another.</p>
 
   <p>When a <code><a href="#document">Document</a></code> is created by a <a href="webappapis.html#concept-script" title="concept-script">script</a> using the <code title="dom-DOMImplementation-createDocument"><a href="infrastructure.html#dom-domimplementation-createdocument">createDocument()</a></code>
   or <code title="dom-DOMHTMLImplementation-createHTMLDocument">createHTMLDocument()</code>
@@ -516,21 +519,24 @@
 
   <dl class="domintro"><dt><var title="">document</var> . <code title="dom-document-referrer"><a href="#dom-document-referrer">referrer</a></code></dt>
    <dd>
-    <p>Returns <a href="#the-document's-current-address" title="the document's current address">the
-    address</a> of the <code><a href="#document">Document</a></code> from which the user
-    navigated to this one, unless it was blocked or there was no such
-    document, in which case it returns the empty string.</p>
+
+    <p>Returns <a href="#the-document's-address" title="the document's address">the address</a>
+    of the <code><a href="#document">Document</a></code> from which the user navigated to this
+    one, unless it was blocked or there was no such document, in which
+    case it returns the empty string.</p>
+
     <p>The <code title="rel-noreferrer"><a href="links.html#link-type-noreferrer">noreferrer</a></code> link
     type can be used to block the referrer.</p>
+
    </dd>
 
   </dl><div class="impl">
 
   <p>The <dfn id="dom-document-referrer" title="dom-document-referrer"><code>referrer</code></dfn> attribute
-  must return either the <a href="#the-document's-current-address" title="the document's current
-  address">current address</a> of the <a href="browsers.html#active-document">active document</a>
-  of the <a href="history.html#source-browsing-context">source browsing context</a> <em>at the time the
-  navigation was started</em> (that is, the page which <a href="history.html#navigate" title="navigate">navigated</a> the <a href="browsers.html#browsing-context">browsing context</a>
+  must return either the <a href="#the-document's-address" title="the document's
+  address">address</a> of the <a href="browsers.html#active-document">active document</a> of the
+  <a href="history.html#source-browsing-context">source browsing context</a> <em>at the time the navigation
+  was started</em> (that is, the page which <a href="history.html#navigate" title="navigate">navigated</a> the <a href="browsers.html#browsing-context">browsing context</a>
   to the current document), with any <a href="urls.html#url-fragment" title="url-fragment">&lt;fragment&gt;</a> component removed; or
   the empty string if there is no such originating page, or if the UA
   has been configured not to report referrers in this case, or if the
@@ -569,7 +575,7 @@
   <code><a href="#document">Document</a></code> was created.</p>
 
   <p>A <code><a href="#document">Document</a></code> object that falls into one of the
-  following conditions is a <dfn id="cookie-free-document-object">cookie-free <code>Document</code>
+  following conditions is a <dfn id="cookie-averse-document-object">cookie-averse <code>Document</code>
   object</dfn>:</p>
 
   <ul><li>A <code><a href="#document">Document</a></code> that has no <a href="browsers.html#browsing-context">browsing
@@ -580,10 +586,10 @@
    authority.</li>
 
   </ul><!--Other specifications can also define <code>Document</code>
-  objects as being <span title="cookie-free Document
-  object">cookie-free <code>Document</code> objects</span>.--><p id="sandboxCookies">On getting, if the document is a
-  <a href="#cookie-free-document-object">cookie-free <code>Document</code> object</a>, then the user
-  agent must return the empty string. Otherwise, if the
+  objects as being <span title="cookie-averse Document
+  object">cookie-averse <code>Document</code> objects</span>.--><p id="sandboxCookies">On getting, if the document is a
+  <a href="#cookie-averse-document-object">cookie-averse <code>Document</code> object</a>, then the
+  user agent must return the empty string. Otherwise, if the
   <code><a href="#document">Document</a></code>'s <a href="browsers.html#origin-0">origin</a> is not a
   scheme/host/port tuple, the user agent must throw a
   <code><a href="infrastructure.html#securityerror">SecurityError</a></code> exception. Otherwise, the user agent must
@@ -592,7 +598,7 @@
   "non-HTTP" API, <a href="infrastructure.html#decoded-as-utf-8,-with-error-handling">decoded as UTF-8, with error handling</a>.
   <a href="references.html#refsCOOKIES">[COOKIES]</a></p>
 
-  <p>On setting, if the document is a <a href="#cookie-free-document-object">cookie-free
+  <p>On setting, if the document is a <a href="#cookie-averse-document-object">cookie-averse
   <code>Document</code> object</a>, then the user agent must do
   nothing. Otherwise, if the <code><a href="#document">Document</a></code>'s
   <a href="browsers.html#origin-0">origin</a> is not a scheme/host/port tuple, the user agent
@@ -673,12 +679,12 @@
 
   <p>Each document has a <dfn id="current-document-readiness">current document readiness</dfn>. When a
   <code><a href="#document">Document</a></code> object is created, it must have its
-  <a href="#current-document-readiness">current document readiness</a> set to the string "<code title="">loading</code>"
-  if the document is associated with an <a href="parsing.html#html-parser">HTML parser</a> or an
-  <a href="the-xhtml-syntax.html#xml-parser">XML parser</a>, or to the string "<code title="">complete</code>" otherwise.
-  Various algorithms during page loading affect this value. When the
-  value is set, the user agent must <a href="webappapis.html#fire-a-simple-event">fire a simple event</a>
-  named <dfn id="event-readystatechange" title="event-readystatechange"><code>readystatechange</code></dfn>
+  <a href="#current-document-readiness">current document readiness</a> set to the string "<code title="">loading</code>" if the document is associated with an
+  <a href="parsing.html#html-parser">HTML parser</a>, an <a href="the-xhtml-syntax.html#xml-parser">XML parser</a>, or an XSLT
+  processor, and to the string "<code title="">complete</code>"
+  otherwise. Various algorithms during page loading affect this value.
+  When the value is set, the user agent must <a href="webappapis.html#fire-a-simple-event">fire a simple
+  event</a> named <dfn id="event-readystatechange" title="event-readystatechange"><code>readystatechange</code></dfn>
   at the <code><a href="#document">Document</a></code> object.</p>
 
   <p>A <code><a href="#document">Document</a></code> is said to have an <dfn id="active-parser">active

Index: index.html
===================================================================
RCS file: /sources/public/html5/spec/index.html,v
retrieving revision 1.1288
retrieving revision 1.1289
diff -u -d -r1.1288 -r1.1289
--- index.html	7 Sep 2012 00:13:58 -0000	1.1288
+++ index.html	7 Sep 2012 11:14:06 -0000	1.1289
@@ -3367,7 +3367,7 @@
 
     </td></tr><tr><td> <code title="event-hashchange"><a href="history.html#event-hashchange">hashchange</a></code>
      </td><td> <code><a href="history.html#hashchangeevent">HashChangeEvent</a></code>
-     </td><td> Fired at the <code><a href="browsers.html#window">Window</a></code> when the fragment identifier part of <a href="dom.html#the-document's-current-address">the document's current address</a> changes
+     </td><td> Fired at the <code><a href="browsers.html#window">Window</a></code> when the fragment identifier part of <a href="dom.html#the-document's-address">the document's address</a> changes
 
     </td></tr><tr><td> <code title="event-input">input</code>
      </td><td> <code><a href="infrastructure.html#event">Event</a></code>

Index: urls.html
===================================================================
RCS file: /sources/public/html5/spec/urls.html,v
retrieving revision 1.232
retrieving revision 1.233
diff -u -d -r1.232 -r1.233
--- urls.html	7 Sep 2012 00:14:07 -0000	1.232
+++ urls.html	7 Sep 2012 11:14:07 -0000	1.233
@@ -591,6 +591,7 @@
 
     <ol><li><p>Let <var title="">fallback base url</var> be <a href="dom.html#the-document's-address">the
      document's address</a>.</p></li>
+     <!-- http://www.hixie.ch/tests/adhoc/dom/level0/history/pushState/001/ -->
 
      <li>
 
@@ -1174,9 +1175,8 @@
    <li>
 
     <p>Generate the <i>address of the resource from which Request-URIs
-    are obtained</i> as required by HTTP for the <code title="http-referer">Referer</code> (sic) header from <a href="dom.html#the-document's-current-address">the
-    document's current address</a> of <var title="">document</var>.
-    <a href="references.html#refsHTTP">[HTTP]</a></p>
+    are obtained</i> as required by HTTP for the <code title="http-referer">Referer</code> (sic) header from <a href="dom.html#the-document's-address">the
+    document's address</a> of <var title="">document</var>. <a href="references.html#refsHTTP">[HTTP]</a></p>
 
     <p>Remove any <a href="#url-fragment" title="url-fragment">&lt;fragment&gt;</a>
     component from the generated <i>address of the resource from which

Index: the-script-element.html
===================================================================
RCS file: /sources/public/html5/spec/the-script-element.html,v
retrieving revision 1.170
retrieving revision 1.171
diff -u -d -r1.170 -r1.171
--- the-script-element.html	7 Sep 2012 00:14:05 -0000	1.170
+++ the-script-element.html	7 Sep 2012 11:14:07 -0000	1.171
@@ -1405,12 +1405,9 @@
 
   <p><i>This section is non-normative.</i></p>
   <p>This specification does not define how XSLT interacts with the
-  <code><a href="#the-script-element">script</a></code> element (or, indeed, how XSLT processing
-  triggers the <a href="the-end.html#stop-parsing">stop parsing</a> steps, how it interacts with
-  the <a href="history.html#navigate" title="navigate">navigation</a> algorithm, or how it
-  fits in with the <a href="webappapis.html#event-loop">event loop</a>). However, in the absence
-  of another specification actually defining this, here are some
-  guidelines for implementors, based on existing implementations:</p>
+  <code><a href="#the-script-element">script</a></code> element. However, in the absence of another
+  specification actually defining this, here are some guidelines for
+  implementors, based on existing implementations:</p>
 
   <ul><li><p>When an XSLT transformation program is triggered by an <code title="">&lt;?xml-stylesheet?&gt;</code> processing instruction and
    the browser implements a direct-to-DOM transformation,

Index: history.html
===================================================================
RCS file: /sources/public/html5/spec/history.html,v
retrieving revision 1.1262
retrieving revision 1.1263
diff -u -d -r1.1262 -r1.1263
--- history.html	7 Sep 2012 00:13:58 -0000	1.1262
+++ history.html	7 Sep 2012 11:14:05 -0000	1.1263
@@ -775,7 +775,8 @@
 
    <li>
 
-    <p>Set <a href="dom.html#the-document's-current-address">the document's current address</a> to <var title="">new URL</var>.</p>
+    <p>Set <a href="dom.html#the-document's-address">the document's address</a> to <var title="">new
+    URL</var>.</p>
 
     <p class="note">Since this is neither a <a href="#navigate" title="navigate">navigation</a> of the <a href="browsers.html#browsing-context">browsing
     context</a> nor a <a href="#traverse-the-history" title="traverse the history">history
@@ -942,10 +943,11 @@
 
   </div>
 
-  <p><code><a href="#location">Location</a></code> objects provide a representation of <a href="dom.html#the-document's-current-address" title="the document's current address">their document's current
-  address</a>, and allow the <a href="#current-entry">current entry</a> of the
-  <a href="browsers.html#browsing-context">browsing context</a>'s session history to be changed, by
-  adding or replacing entries in the <code title="dom-history"><a href="#dom-history">history</a></code> object.</p>
+  <p><code><a href="#location">Location</a></code> objects provide a representation of <a href="dom.html#the-document's-address" title="the document's address">their document's address</a>, and
+  allow the <a href="#current-entry">current entry</a> of the <a href="browsers.html#browsing-context">browsing
+  context</a>'s session history to be changed, by adding or
+  replacing entries in the <code title="dom-history"><a href="#dom-history">history</a></code>
+  object.</p>
 
   <pre class="idl">interface <dfn id="location">Location</dfn> {
   stringifier attribute DOMString <a href="#dom-location-href" title="dom-location-href">href</a>;
@@ -1000,9 +1002,9 @@
   </dl><div class="impl">
 
   <p>The <dfn id="dom-location-href" title="dom-location-href"><code>href</code></dfn>
-  attribute must return <a href="dom.html#the-document's-current-address" title="the document's current
-  address">the current address</a> of the associated
-  <code><a href="dom.html#document">Document</a></code> object, as an <a href="urls.html#absolute-url">absolute URL</a>.</p>
+  attribute must return <a href="dom.html#the-document's-address" title="the document's address">the
+  address</a> of the associated <code><a href="dom.html#document">Document</a></code> object, as an
+  <a href="urls.html#absolute-url">absolute URL</a>.</p>
 
   <p>On setting, if the <code><a href="#location">Location</a></code> object's associated
   <code><a href="dom.html#document">Document</a></code> object has <a href="the-end.html#completely-loaded">completely loaded</a>,
@@ -1071,7 +1073,7 @@
    <dt>Otherwise</dt>
 
    <dd><p><a href="#navigate">Navigate</a><!--DONAV location.reload()--> the
-   <a href="browsers.html#browsing-context">browsing context</a> to <a href="dom.html#the-document's-current-address">the document's current
+   <a href="browsers.html#browsing-context">browsing context</a> to <a href="dom.html#the-document's-address">the document's
    address</a> with <a href="#replacement-enabled">replacement enabled</a>. The
    <a href="#source-browsing-context">source browsing context</a> must be the <a href="browsers.html#browsing-context">browsing
    context</a> being navigated.</p></dd> <!-- it appears that
@@ -1098,14 +1100,13 @@
 
   <p>The <code><a href="#location">Location</a></code> interface also has the complement of
   <a href="urls.html#url-decomposition-idl-attributes">URL decomposition IDL attributes</a>, <dfn id="dom-location-protocol" title="dom-location-protocol"><code>protocol</code></dfn>, <dfn id="dom-location-host" title="dom-location-host"><code>host</code></dfn>, <dfn id="dom-location-port" title="dom-location-port"><code>port</code></dfn>, <dfn id="dom-location-hostname" title="dom-location-hostname"><code>hostname</code></dfn>, <dfn id="dom-location-pathname" title="dom-location-pathname"><code>pathname</code></dfn>, <dfn id="dom-location-search" title="dom-location-search"><code>search</code></dfn>, and <dfn id="dom-location-hash" title="dom-location-hash"><code>hash</code></dfn>. <span class="impl">These must follow the rules given for <a href="urls.html#url-decomposition-idl-attributes">URL
-  decomposition IDL attributes</a>, with the <a href="urls.html#concept-uda-input" title="concept-uda-input">input</a> being <a href="dom.html#the-document's-current-address" title="the
-  document's current address">the current address</a> of the
-  associated <code><a href="dom.html#document">Document</a></code> object, as an <a href="urls.html#absolute-url">absolute
-  URL</a> (same as the <code title="dom-location-href"><a href="#dom-location-href">href</a></code>
-  attribute), and the <a href="urls.html#concept-uda-setter" title="concept-uda-setter">common setter
-  action</a> being the same as setting the <code title="dom-location-href"><a href="#dom-location-href">href</a></code> attribute to the new output
-  value.</span></p>
-<!--TOPIC:HTML-->
+  decomposition IDL attributes</a>, with the <a href="urls.html#concept-uda-input" title="concept-uda-input">input</a> being <a href="dom.html#the-document's-address" title="the
+  document's address">the address</a> of the associated
+  <code><a href="dom.html#document">Document</a></code> object, as an <a href="urls.html#absolute-url">absolute URL</a> (same
+  as the <code title="dom-location-href"><a href="#dom-location-href">href</a></code> attribute), and
+  the <a href="urls.html#concept-uda-setter" title="concept-uda-setter">common setter action</a>
+  being the same as setting the <code title="dom-location-href"><a href="#dom-location-href">href</a></code> attribute to the new output
+  value.</span></p> <!--TOPIC:HTML-->
 
 
 <!--ADD-TOPIC:Security-->
@@ -1777,10 +1778,9 @@
    these steps.</p></li>
 
    <li><p><a href="#scroll-to-the-fragment-identifier">Scroll to the fragment identifier</a> given in
-   <a href="dom.html#the-document's-current-address">the document's current address</a>. If this fails to find
-   <a href="#the-indicated-part-of-the-document" title="the indicated part of the document">an indicated part
-   of the document</a>, then return to the <i>fragment identifier
-   loop</i> step.</p></li>
+   <a href="dom.html#the-document's-address">the document's address</a>. If this fails to find <a href="#the-indicated-part-of-the-document" title="the indicated part of the document">an indicated part of the
+   document</a>, then return to the <i>fragment identifier loop</i>
+   step.</p></li>
 
   </ol><p>The <a href="webappapis.html#task-source">task source</a> for this <a href="webappapis.html#concept-task" title="concept-task">task</a> is the <a href="webappapis.html#networking-task-source">networking task
   source</a>.</p>
@@ -2129,7 +2129,7 @@
 
    <li><p><a href="#traverse-the-history">Traverse the history</a> to the new entry. This
    will <a href="#scroll-to-the-fragment-identifier">scroll to the fragment identifier</a> given in what
-   is now <a href="dom.html#the-document's-current-address">the document's current address</a>.</p></li>
+   is now <a href="dom.html#the-document's-address">the document's address</a>.</p></li>
 
   </ol><p class="note">If the scrolling fails because the relevant <a href="infrastructure.html#concept-id" title="concept-id">ID</a> has not yet been parsed, then the
   original <a href="#navigate" title="navigate">navigation</a> algorithm will
@@ -2312,8 +2312,8 @@
 
     </ol></li>
 
-   <li><p>Set <a href="dom.html#the-document's-current-address">the document's current address</a> to the URL
-   of the <var title="">specified entry</var>.</p></li>
+   <li><p>Set <a href="dom.html#the-document's-address">the document's address</a> to the URL of the
+   <var title="">specified entry</var>.</p></li>
 
    <li><p>If the <var title="">specified entry</var> has a URL whose
    fragment identifier differs from that of the <a href="#current-entry">current

Index: commands.html
===================================================================
RCS file: /sources/public/html5/spec/commands.html,v
retrieving revision 1.221
retrieving revision 1.222
diff -u -d -r1.221 -r1.222
--- commands.html	7 Sep 2012 00:13:56 -0000	1.221
+++ commands.html	7 Sep 2012 11:14:05 -0000	1.222
@@ -629,7 +629,11 @@
   of the command is always false. (The command is never checked.)</p>
 
   <p>The <a href="#command-facet-action" title="command-facet-Action">Action</a> of the
-  command is to <a href="webappapis.html#fire-a-click-event" title="fire a click event">fire a <code title="event-click">click</code> event</a> at the element.</p>
+  command, if the element has a defined <a href="content-models.html#activation-behavior">activation
+  behavior</a>, is to <a href="content-models.html#run-synthetic-click-activation-steps">run synthetic click activation
+  steps</a> on the element. Otherwise, it is just to <a href="webappapis.html#fire-a-click-event">fire a
+  <code title="event-click">click</code> event</a> at the
+  element.</p>
 
 
   <h5 id="using-the-button-element-to-define-a-command"><span class="secno">4.11.5.2 </span><dfn title="button-command">Using the <code>button</code> element to define a command</dfn></h5>

Index: acknowledgements.html
===================================================================
RCS file: /sources/public/html5/spec/acknowledgements.html,v
retrieving revision 1.1274
retrieving revision 1.1275
diff -u -d -r1.1274 -r1.1275
--- acknowledgements.html	7 Sep 2012 00:13:55 -0000	1.1274
+++ acknowledgements.html	7 Sep 2012 11:14:05 -0000	1.1275
@@ -536,7 +536,7 @@
   Elliott Sprehn,
   Elliotte Harold,
   Eric Carlson,
-  Eric Law,
+  Eric Lawrence,
   Eric Rescorla,
   Eric Semling,
   Erik Arvidsson,


Index: global-attributes.html
===================================================================
RCS file: /sources/public/html5/spec/global-attributes.html,v
retrieving revision 1.171
retrieving revision 1.172
diff -u -d -r1.171 -r1.172
--- global-attributes.html	7 Sep 2012 00:13:57 -0000	1.171
+++ global-attributes.html	7 Sep 2012 11:14:05 -0000	1.172
@@ -1021,9 +1021,9 @@
 
   <div class="impl">
 
-  <hr><p>The <dfn id="dom-classname" title="dom-className"><code>className</code></dfn> and
-  <dfn id="dom-classlist" title="dom-classList"><code>classList</code></dfn> IDL
-  attributes must both <a href="common-dom-interfaces.html#reflect">reflect</a> the <code title="attr-class"><a href="#classes">class</a></code> content attribute.</p>
+  <hr><p class="note">The <dfn id="dom-classname" title="dom-className"><code>className</code></dfn> and <dfn id="dom-classlist" title="dom-classList"><code>classList</code></dfn> IDL attributes,
+  defined in the DOM Core specification, <a href="common-dom-interfaces.html#reflect">reflect</a> the
+  <code title="attr-class"><a href="#classes">class</a></code> content attribute. <a href="references.html#refsDOMCORE">[DOMCORE]</a></p>
 
   </div>
 

Index: the-meta-element.html
===================================================================
RCS file: /sources/public/html5/spec/the-meta-element.html,v
retrieving revision 1.171
retrieving revision 1.172
diff -u -d -r1.171 -r1.172
--- the-meta-element.html	7 Sep 2012 00:14:04 -0000	1.171
+++ the-meta-element.html	7 Sep 2012 11:14:07 -0000	1.172
@@ -1172,17 +1172,21 @@
   the other is <meta charset>, and the encoding is UTF-8. -->
 
   <p>If an <a href="infrastructure.html#html-documents" title="HTML documents">HTML document</a> does not
-  start with a BOM, and if its encoding is not explicitly given by
-  <a href="urls.html#content-type" title="Content-Type">Content-Type metadata</a>, and the
-  document is not <a href="the-iframe-element.html#an-iframe-srcdoc-document">an <code>iframe</code> <code title="attr-iframe-srcdoc">srcdoc</code> document</a>, then the
+  start with a BOM, and its encoding is not explicitly given by <a href="urls.html#content-type" title="Content-Type">Content-Type metadata</a>, and the document
+  is not <a href="the-iframe-element.html#an-iframe-srcdoc-document">an <code>iframe</code> <code title="attr-iframe-srcdoc">srcdoc</code> document</a>, then the
   character encoding used must be an <a href="infrastructure.html#ascii-compatible-character-encoding">ASCII-compatible character
-  encoding</a>, and, in addition, if that encoding isn't US-ASCII
-  itself, then the encoding must be specified using a
+  encoding</a>, and the encoding must be specified using a
   <code><a href="#the-meta-element">meta</a></code> element with a <code title="attr-meta-charset"><a href="#attr-meta-charset">charset</a></code> attribute or a
   <code><a href="#the-meta-element">meta</a></code> element with an <code title="attr-meta-http-equiv"><a href="#attr-meta-http-equiv">http-equiv</a></code> attribute in the
   <a href="#attr-meta-http-equiv-content-type" title="attr-meta-http-equiv-content-type">Encoding declaration
   state</a>.</p>
 
+  <p class="note">A character encoding declaration is required (either
+  in the <a href="urls.html#content-type" title="Content-Type">Content-Type metadata</a> or
+  explicitly in the file) even if the encoding is US-ASCII, because an
+  encoding is needed to process non-ASCII characters entered by the
+  user in forms, in URLs generated by scripts, and so forth.</p>
+
   <p>If the document is <a href="the-iframe-element.html#an-iframe-srcdoc-document">an <code>iframe</code> <code title="attr-iframe-srcdoc">srcdoc</code> document</a>, the
   document must not have a <a href="#character-encoding-declaration">character encoding
   declaration</a>. (In this case, the source is already decoded,

Index: browsers.html
===================================================================
RCS file: /sources/public/html5/spec/browsers.html,v
retrieving revision 1.1257
retrieving revision 1.1258
diff -u -d -r1.1257 -r1.1258
--- browsers.html	7 Sep 2012 00:13:56 -0000	1.1257
+++ browsers.html	7 Sep 2012 11:14:05 -0000	1.1258
@@ -1503,9 +1503,10 @@
   on <code><a href="#window">Window</a></code> objects should, if there is an existing
   attempt to <a href="history.html#navigate">navigate</a> the <a href="#browsing-context">browsing context</a>
   and that attempt is not currently running the <a href="history.html#unload-a-document">unload a
-  document</a> algorithm, cancel that <a href="history.html#navigate" title="navigate">navigation</a> and any associated instances of
-  the <a href="urls.html#fetch" title="fetch">fetch algorithm</a>. Otherwise, it must
-  do nothing.</p>
+  document</a> algorithm, cancel that <a href="history.html#navigate" title="navigate">navigation</a>; then, it must <a href="history.html#abort-a-document" title="abort
+  a document">abort</a> the <a href="#active-document">active document</a> of the
+  <a href="#browsing-context">browsing context</a> of the <code><a href="#window">Window</a></code> object on
+  which it was invoked.</p>
 
   </div>
 

Index: single-page.html
===================================================================
RCS file: /sources/public/html5/spec/single-page.html,v
retrieving revision 1.94
retrieving revision 1.95
diff -u -d -r1.94 -r1.95
--- single-page.html	7 Sep 2012 08:43:50 -0000	1.94
+++ single-page.html	7 Sep 2012 11:14:06 -0000	1.95
@@ -7256,6 +7256,7 @@
 
     <ol><li><p>Let <var title="">fallback base url</var> be <a href="#the-document's-address">the
      document's address</a>.</p></li>
+     <!-- http://www.hixie.ch/tests/adhoc/dom/level0/history/pushState/001/ -->
 
      <li>
 
@@ -7839,9 +7840,8 @@
    <li>
 
     <p>Generate the <i>address of the resource from which Request-URIs
-    are obtained</i> as required by HTTP for the <code title=http-referer>Referer</code> (sic) header from <a href="#the-document's-current-address">the
-    document's current address</a> of <var title="">document</var>.
-    <a href=#refsHTTP>[HTTP]</a></p>
+    are obtained</i> as required by HTTP for the <code title=http-referer>Referer</code> (sic) header from <a href="#the-document's-address">the
+    document's address</a> of <var title="">document</var>. <a href=#refsHTTP>[HTTP]</a></p>
 
     <p>Remove any <a href=#url-fragment title=url-fragment>&lt;fragment&gt;</a>
     component from the generated <i>address of the resource from which
@@ -9385,18 +9385,21 @@
   <code><a href=#document>Document</a></code> object. <a href=#refsDOMCORE>[DOMCORE]</a></p>
 
   <p><dfn id="the-document's-address">The document's address</dfn> is an <a href=#absolute-url>absolute URL</a>
-  that is set when the <code><a href=#document>Document</a></code> is created. <dfn id="the-document's-current-address">The
-  document's current address</dfn> is an <a href=#absolute-url>absolute URL</a>
+  that is initially set when the <code><a href=#document>Document</a></code> is created but
   that can change during the lifetime of the <code><a href=#document>Document</a></code>,
   for example when the user <a href=#navigate title=navigate>navigates</a> to
   a <a href=#scroll-to-fragid title=navigate-fragid>fragment identifier</a> on the
   page or when the <code title=dom-history-pushState><a href=#dom-history-pushstate>pushState()</a></code> method is called
-  with a new <a href=#url>URL</a>. <span class=impl><a href="#the-document's-current-address">The document's
-  current address</a> must be set to <a href="#the-document's-address">the document's
-  address</a> when the <code><a href=#document>Document</a></code> is created.</span></p>
+  with a new <a href=#url>URL</a>.</p>
+  <!--
+    http://www.hixie.ch/tests/adhoc/dom/level0/history/pushState/002/
+    http://www.hixie.ch/tests/adhoc/html/navigation/fragids/016.html
+  -->
 
-  <p class=note>Interactive user agents typically expose <a href="#the-document's-current-address">the
-  document's current address</a> in their user interface.</p>
+  <p class=warning>Interactive user agents typically expose
+  <a href="#the-document's-address">the document's address</a> in their user interface. This is
+  the primary mechanism by which a user can tell if a site is
+  attempting to impersonate another.</p>
 
   <p>When a <code><a href=#document>Document</a></code> is created by a <a href=#concept-script title=concept-script>script</a> using the <code title=dom-DOMImplementation-createDocument><a href=#dom-domimplementation-createdocument>createDocument()</a></code>
   or <code title=dom-DOMHTMLImplementation-createHTMLDocument>createHTMLDocument()</code>
@@ -9558,21 +9561,24 @@
 
   <dl class=domintro><dt><var title="">document</var> . <code title=dom-document-referrer><a href=#dom-document-referrer>referrer</a></code></dt>
    <dd>
-    <p>Returns <a href="#the-document's-current-address" title="the document's current address">the
-    address</a> of the <code><a href=#document>Document</a></code> from which the user
-    navigated to this one, unless it was blocked or there was no such
-    document, in which case it returns the empty string.</p>
+
+    <p>Returns <a href="#the-document's-address" title="the document's address">the address</a>
+    of the <code><a href=#document>Document</a></code> from which the user navigated to this
+    one, unless it was blocked or there was no such document, in which
+    case it returns the empty string.</p>
+
     <p>The <code title=rel-noreferrer><a href=#link-type-noreferrer>noreferrer</a></code> link
     type can be used to block the referrer.</p>
+
    </dd>
 
   </dl><div class=impl>
 
   <p>The <dfn id=dom-document-referrer title=dom-document-referrer><code>referrer</code></dfn> attribute
-  must return either the <a href="#the-document's-current-address" title="the document's current
-  address">current address</a> of the <a href=#active-document>active document</a>
-  of the <a href=#source-browsing-context>source browsing context</a> <em>at the time the
-  navigation was started</em> (that is, the page which <a href=#navigate title=navigate>navigated</a> the <a href=#browsing-context>browsing context</a>
+  must return either the <a href="#the-document's-address" title="the document's
+  address">address</a> of the <a href=#active-document>active document</a> of the
+  <a href=#source-browsing-context>source browsing context</a> <em>at the time the navigation
+  was started</em> (that is, the page which <a href=#navigate title=navigate>navigated</a> the <a href=#browsing-context>browsing context</a>
   to the current document), with any <a href=#url-fragment title=url-fragment>&lt;fragment&gt;</a> component removed; or
   the empty string if there is no such originating page, or if the UA
   has been configured not to report referrers in this case, or if the
@@ -9611,7 +9617,7 @@
   <code><a href=#document>Document</a></code> was created.</p>
 
   <p>A <code><a href=#document>Document</a></code> object that falls into one of the
-  following conditions is a <dfn id=cookie-free-document-object>cookie-free <code>Document</code>
+  following conditions is a <dfn id=cookie-averse-document-object>cookie-averse <code>Document</code>
   object</dfn>:</p>
 
   <ul><li>A <code><a href=#document>Document</a></code> that has no <a href=#browsing-context>browsing
@@ -9622,10 +9628,10 @@
    authority.</li>
 
   </ul><!--Other specifications can also define <code>Document</code>
-  objects as being <span title="cookie-free Document
-  object">cookie-free <code>Document</code> objects</span>.--><p id=sandboxCookies>On getting, if the document is a
-  <a href=#cookie-free-document-object>cookie-free <code>Document</code> object</a>, then the user
-  agent must return the empty string. Otherwise, if the
+  objects as being <span title="cookie-averse Document
+  object">cookie-averse <code>Document</code> objects</span>.--><p id=sandboxCookies>On getting, if the document is a
+  <a href=#cookie-averse-document-object>cookie-averse <code>Document</code> object</a>, then the
+  user agent must return the empty string. Otherwise, if the
   <code><a href=#document>Document</a></code>'s <a href=#origin-0>origin</a> is not a
   scheme/host/port tuple, the user agent must throw a
   <code><a href=#securityerror>SecurityError</a></code> exception. Otherwise, the user agent must
@@ -9634,7 +9640,7 @@
   "non-HTTP" API, <a href=#decoded-as-utf-8,-with-error-handling>decoded as UTF-8, with error handling</a>.
   <a href=#refsCOOKIES>[COOKIES]</a></p>
 
-  <p>On setting, if the document is a <a href=#cookie-free-document-object>cookie-free
+  <p>On setting, if the document is a <a href=#cookie-averse-document-object>cookie-averse
   <code>Document</code> object</a>, then the user agent must do
   nothing. Otherwise, if the <code><a href=#document>Document</a></code>'s
   <a href=#origin-0>origin</a> is not a scheme/host/port tuple, the user agent
@@ -9715,12 +9721,12 @@
 
   <p>Each document has a <dfn id=current-document-readiness>current document readiness</dfn>. When a
   <code><a href=#document>Document</a></code> object is created, it must have its
-  <a href=#current-document-readiness>current document readiness</a> set to the string "<code title="">loading</code>"
-  if the document is associated with an <a href=#html-parser>HTML parser</a> or an
-  <a href=#xml-parser>XML parser</a>, or to the string "<code title="">complete</code>" otherwise.
-  Various algorithms during page loading affect this value. When the
-  value is set, the user agent must <a href=#fire-a-simple-event>fire a simple event</a>
-  named <dfn id=event-readystatechange title=event-readystatechange><code>readystatechange</code></dfn>
+  <a href=#current-document-readiness>current document readiness</a> set to the string "<code title="">loading</code>" if the document is associated with an
+  <a href=#html-parser>HTML parser</a>, an <a href=#xml-parser>XML parser</a>, or an XSLT
+  processor, and to the string "<code title="">complete</code>"
+  otherwise. Various algorithms during page loading affect this value.
+  When the value is set, the user agent must <a href=#fire-a-simple-event>fire a simple
+  event</a> named <dfn id=event-readystatechange title=event-readystatechange><code>readystatechange</code></dfn>
   at the <code><a href=#document>Document</a></code> object.</p>
 
   <p>A <code><a href=#document>Document</a></code> is said to have an <dfn id=active-parser>active
@@ -10376,8 +10382,6 @@
            attribute DOMString <a href=#dom-lang title=dom-lang>lang</a>;
            attribute boolean <a href=#dom-translate title=dom-translate>translate</a>;
            attribute DOMString <a href=#dom-dir title=dom-dir>dir</a>;
-           attribute <span>DOMString</span> <a href=#dom-classname title=dom-className>className</a>;
-  readonly attribute <a href=#domtokenlist>DOMTokenList</a> <a href=#dom-classlist title=dom-classList>classList</a>;
   readonly attribute <a href=#domstringmap-0>DOMStringMap</a> <a href=#dom-dataset title=dom-dataset>dataset</a>;
 
 <!--MD-->
@@ -11169,9 +11173,9 @@
 
   <div class=impl>
 
-  <hr><p>The <dfn id=dom-classname title=dom-className><code>className</code></dfn> and
-  <dfn id=dom-classlist title=dom-classList><code>classList</code></dfn> IDL
-  attributes must both <a href=#reflect>reflect</a> the <code title=attr-class><a href=#classes>class</a></code> content attribute.</p>
+  <hr><p class=note>The <dfn id=dom-classname title=dom-className><code>className</code></dfn> and <dfn id=dom-classlist title=dom-classList><code>classList</code></dfn> IDL attributes,
+  defined in the DOM Core specification, <a href=#reflect>reflect</a> the
+  <code title=attr-class><a href=#classes>class</a></code> content attribute. <a href=#refsDOMCORE>[DOMCORE]</a></p>
 
   </div>
 
@@ -13139,9 +13143,25 @@
   unaffected.) <a href=#refsXSLT10>[XSLT10]</a></p> <!-- note:
   version matters for this ref -->
 
-  <p class=note>There are also additional comments regarding the
-  interaction of XSLT and HTML <a href=#scriptTagXSLT>in the
-  <code>script</code> element section</a>.</p>
+  <hr><p>This specification does not specify precisely how XSLT processing
+  interacts with the <a href=#html-parser>HTML parser</a> infrastructure (for
+  example, whether an XSLT processor acts as if it puts any elements
+  into a <a href=#stack-of-open-elements>stack of open elements</a>). However, XSLT
+  processors must <a href=#stop-parsing>stop parsing</a> if they successfully
+  complete, and must set the <a href=#current-document-readiness>current document readiness</a>
+  first to "<code title="">interactive</code>"<!-- this synchronously
+  fires an event --> and then to "<code title="">complete</code>"<!--
+  this also synchronously fires an event --> if they are aborted.</p>
+
+  <hr><p>This specification does not specify how XSLT interacts with the
+  <a href=#navigate title=navigate>navigation</a> algorithm, how it fits in
+  with the <a href=#event-loop>event loop</a>, nor how error pages are to be
+  handled (e.g. whether XSLT errors are to replace an incremental XSLT
+  output, or are rendered inline, etc).</p>
+
+  <p class=note>There are also additional non-normative comments
+  regarding the interaction of XSLT and HTML <a href=#scriptTagXSLT>in the <code>script</code> element
+  section</a>.</p>
 
   </div>
 
@@ -15118,17 +15138,21 @@
   the other is <meta charset>, and the encoding is UTF-8. -->
 
   <p>If an <a href=#html-documents title="HTML documents">HTML document</a> does not
-  start with a BOM, and if its encoding is not explicitly given by
-  <a href=#content-type title=Content-Type>Content-Type metadata</a>, and the
-  document is not <a href=#an-iframe-srcdoc-document>an <code>iframe</code> <code title=attr-iframe-srcdoc>srcdoc</code> document</a>, then the
+  start with a BOM, and its encoding is not explicitly given by <a href=#content-type title=Content-Type>Content-Type metadata</a>, and the document
+  is not <a href=#an-iframe-srcdoc-document>an <code>iframe</code> <code title=attr-iframe-srcdoc>srcdoc</code> document</a>, then the
   character encoding used must be an <a href=#ascii-compatible-character-encoding>ASCII-compatible character
-  encoding</a>, and, in addition, if that encoding isn't US-ASCII
-  itself, then the encoding must be specified using a
+  encoding</a>, and the encoding must be specified using a
   <code><a href=#the-meta-element>meta</a></code> element with a <code title=attr-meta-charset><a href=#attr-meta-charset>charset</a></code> attribute or a
   <code><a href=#the-meta-element>meta</a></code> element with an <code title=attr-meta-http-equiv><a href=#attr-meta-http-equiv>http-equiv</a></code> attribute in the
   <a href=#attr-meta-http-equiv-content-type title=attr-meta-http-equiv-content-type>Encoding declaration
   state</a>.</p>
 
+  <p class=note>A character encoding declaration is required (either
+  in the <a href=#content-type title=Content-Type>Content-Type metadata</a> or
+  explicitly in the file) even if the encoding is US-ASCII, because an
+  encoding is needed to process non-ASCII characters entered by the
+  user in forms, in URLs generated by scripts, and so forth.</p>
+
   <p>If the document is <a href=#an-iframe-srcdoc-document>an <code>iframe</code> <code title=attr-iframe-srcdoc>srcdoc</code> document</a>, the
   document must not have a <a href=#character-encoding-declaration>character encoding
   declaration</a>. (In this case, the source is already decoded,
@@ -16724,12 +16748,9 @@
 
   <p><i>This section is non-normative.</i></p>
   <p>This specification does not define how XSLT interacts with the
-  <code><a href=#the-script-element>script</a></code> element (or, indeed, how XSLT processing
-  triggers the <a href=#stop-parsing>stop parsing</a> steps, how it interacts with
-  the <a href=#navigate title=navigate>navigation</a> algorithm, or how it
-  fits in with the <a href=#event-loop>event loop</a>). However, in the absence
-  of another specification actually defining this, here are some
-  guidelines for implementors, based on existing implementations:</p>
+  <code><a href=#the-script-element>script</a></code> element. However, in the absence of another
+  specification actually defining this, here are some guidelines for
+  implementors, based on existing implementations:</p>
 
   <ul><li><p>When an XSLT transformation program is triggered by an <code title="">&lt;?xml-stylesheet?&gt;</code> processing instruction and
    the browser implements a direct-to-DOM transformation,
@@ -48512,19 +48533,43 @@
   <p>If the platform supports letting the user submit a form
   implicitly (for example, on some platforms hitting the "enter" key
   while a text field is focused implicitly submits the form), then
-  doing so must cause the form's <a href=#default-button>default button</a>'s
-  <a href=#activation-behavior>activation behavior</a>, if any, to be run.</p>
+  doing so for a form whose <a href=#default-button>default button</a> has a defined
+  <a href=#activation-behavior>activation behavior</a> must cause the user agent to
+  <a href=#run-synthetic-click-activation-steps>run synthetic click activation steps</a> on that
+  <a href=#default-button>default button</a>.</p>
 
   <p class=note>Consequently, if the <a href=#default-button>default button</a> is
   <a href=#concept-fe-disabled title=concept-fe-disabled>disabled</a>, the form is not
   submitted when such an implicit submission mechanism is used. (A
   button has no <a href=#activation-behavior>activation behavior</a> when disabled.)</p>
 
-  <p>If the form has no <a href=#concept-submit-button title=concept-submit-button>submit
-  button</a>, then the implicit submission mechanism must just
+  <p><!-- For Web compatibility reasons caused by obscure historical
+  accidents, -->If the form has no <a href=#concept-submit-button title=concept-submit-button>submit button</a>, then the
+  implicit submission mechanism must do nothing if the form has more
+  than one <i>field that blocks implicit submission</i>, and must
   <a href=#concept-form-submit title=concept-form-submit>submit</a> the
-  <code><a href=#the-form-element>form</a></code> element from the <code><a href=#the-form-element>form</a></code> element
-  itself.</p>
+  <code><a href=#the-form-element>form</a></code> element from the <code><a href=#the-form-element>form</a></code> element itself
+  otherwise.</p>
+
+  <p>For the purpose of the previous paragraph, an element is a
+  <i>field that blocks implicit submission</i> of a <code><a href=#the-form-element>form</a></code>
+  element if it is an <code><a href=#the-input-element>input</a></code> element whose <a href=#form-owner>form
+  owner</a> is that <code><a href=#the-form-element>form</a></code> element and whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in one of the
+  following states:
+  <a href="#text-(type=text)-state-and-search-state-(type=search)" title=attr-input-type-text>Text</a>,
+  <a href="#text-(type=text)-state-and-search-state-(type=search)" title=attr-input-type-search>Search</a>,
+  <a href="#url-state-(type=url)" title=attr-input-type-url>URL</a>,
+  <a href="#telephone-state-(type=tel)" title=attr-input-type-tel>Telephone</a>,
+  <a href="#e-mail-state-(type=email)" title=attr-input-type-email>E-mail</a>,
+  <a href="#password-state-(type=password)" title=attr-input-type-password>Password</a>,
+  <a href="#date-and-time-state-(type=datetime)" title=attr-input-type-datetime>Date and Time</a>,
+  <a href="#date-state-(type=date)" title=attr-input-type-date>Date</a>,
+  <a href="#month-state-(type=month)" title=attr-input-type-month>Month</a>,
+  <a href="#week-state-(type=week)" title=attr-input-type-week>Week</a>,
+  <a href="#time-state-(type=time)" title=attr-input-type-time>Time</a>,
+  <a href="#local-date-and-time-state-(type=datetime-local)" title=attr-input-type-datetime-local>Local Date and Time</a>,
+  <a href="#number-state-(type=number)" title=attr-input-type-number>Number</a>
+  </p>
 
   </div>
 
@@ -50551,7 +50596,11 @@
   of the command is always false. (The command is never checked.)</p>
 
   <p>The <a href=#command-facet-action title=command-facet-Action>Action</a> of the
-  command is to <a href=#fire-a-click-event title="fire a click event">fire a <code title=event-click>click</code> event</a> at the element.</p>
+  command, if the element has a defined <a href=#activation-behavior>activation
+  behavior</a>, is to <a href=#run-synthetic-click-activation-steps>run synthetic click activation
+  steps</a> on the element. Otherwise, it is just to <a href=#fire-a-click-event>fire a
+  <code title=event-click>click</code> event</a> at the
+  element.</p>
 
 
   <h5 id=using-the-button-element-to-define-a-command><span class=secno>4.11.5.2 </span><dfn title=button-command>Using the <code>button</code> element to define a command</dfn></h5>
@@ -54675,9 +54724,10 @@
   on <code><a href=#window>Window</a></code> objects should, if there is an existing
   attempt to <a href=#navigate>navigate</a> the <a href=#browsing-context>browsing context</a>
   and that attempt is not currently running the <a href=#unload-a-document>unload a
-  document</a> algorithm, cancel that <a href=#navigate title=navigate>navigation</a> and any associated instances of
-  the <a href=#fetch title=fetch>fetch algorithm</a>. Otherwise, it must
-  do nothing.</p>
+  document</a> algorithm, cancel that <a href=#navigate title=navigate>navigation</a>; then, it must <a href=#abort-a-document title="abort
+  a document">abort</a> the <a href=#active-document>active document</a> of the
+  <a href=#browsing-context>browsing context</a> of the <code><a href=#window>Window</a></code> object on
+  which it was invoked.</p>
 
   </div>
 
@@ -56349,7 +56399,8 @@
 
    <li>
 
-    <p>Set <a href="#the-document's-current-address">the document's current address</a> to <var title="">new URL</var>.</p>
+    <p>Set <a href="#the-document's-address">the document's address</a> to <var title="">new
+    URL</var>.</p>
 
     <p class=note>Since this is neither a <a href=#navigate title=navigate>navigation</a> of the <a href=#browsing-context>browsing
     context</a> nor a <a href=#traverse-the-history title="traverse the history">history
@@ -56516,10 +56567,11 @@
 
   </div>
 
-  <p><code><a href=#location>Location</a></code> objects provide a representation of <a href="#the-document's-current-address" title="the document's current address">their document's current
-  address</a>, and allow the <a href=#current-entry>current entry</a> of the
-  <a href=#browsing-context>browsing context</a>'s session history to be changed, by
-  adding or replacing entries in the <code title=dom-history><a href=#dom-history>history</a></code> object.</p>
+  <p><code><a href=#location>Location</a></code> objects provide a representation of <a href="#the-document's-address" title="the document's address">their document's address</a>, and
+  allow the <a href=#current-entry>current entry</a> of the <a href=#browsing-context>browsing
+  context</a>'s session history to be changed, by adding or
+  replacing entries in the <code title=dom-history><a href=#dom-history>history</a></code>
+  object.</p>
 
   <pre class=idl>interface <dfn id=location>Location</dfn> {
   stringifier attribute DOMString <a href=#dom-location-href title=dom-location-href>href</a>;
@@ -56574,9 +56626,9 @@
   </dl><div class=impl>
 
   <p>The <dfn id=dom-location-href title=dom-location-href><code>href</code></dfn>
-  attribute must return <a href="#the-document's-current-address" title="the document's current
-  address">the current address</a> of the associated
-  <code><a href=#document>Document</a></code> object, as an <a href=#absolute-url>absolute URL</a>.</p>
+  attribute must return <a href="#the-document's-address" title="the document's address">the
+  address</a> of the associated <code><a href=#document>Document</a></code> object, as an
+  <a href=#absolute-url>absolute URL</a>.</p>
 
   <p>On setting, if the <code><a href=#location>Location</a></code> object's associated
   <code><a href=#document>Document</a></code> object has <a href=#completely-loaded>completely loaded</a>,
@@ -56645,7 +56697,7 @@
    <dt>Otherwise</dt>
 
    <dd><p><a href=#navigate>Navigate</a><!--DONAV location.reload()--> the
-   <a href=#browsing-context>browsing context</a> to <a href="#the-document's-current-address">the document's current
+   <a href=#browsing-context>browsing context</a> to <a href="#the-document's-address">the document's
    address</a> with <a href=#replacement-enabled>replacement enabled</a>. The
    <a href=#source-browsing-context>source browsing context</a> must be the <a href=#browsing-context>browsing
    context</a> being navigated.</p></dd> <!-- it appears that
@@ -56672,14 +56724,13 @@
 
   <p>The <code><a href=#location>Location</a></code> interface also has the complement of
   <a href=#url-decomposition-idl-attributes>URL decomposition IDL attributes</a>, <dfn id=dom-location-protocol title=dom-location-protocol><code>protocol</code></dfn>, <dfn id=dom-location-host title=dom-location-host><code>host</code></dfn>, <dfn id=dom-location-port title=dom-location-port><code>port</code></dfn>, <dfn id=dom-location-hostname title=dom-location-hostname><code>hostname</code></dfn>, <dfn id=dom-location-pathname title=dom-location-pathname><code>pathname</code></dfn>, <dfn id=dom-location-search title=dom-location-search><code>search</code></dfn>, and <dfn id=dom-location-hash title=dom-location-hash><code>hash</code></dfn>. <span class=impl>These must follow the rules given for <a href=#url-decomposition-idl-attributes>URL
-  decomposition IDL attributes</a>, with the <a href=#concept-uda-input title=concept-uda-input>input</a> being <a href="#the-document's-current-address" title="the
-  document's current address">the current address</a> of the
-  associated <code><a href=#document>Document</a></code> object, as an <a href=#absolute-url>absolute
-  URL</a> (same as the <code title=dom-location-href><a href=#dom-location-href>href</a></code>
-  attribute), and the <a href=#concept-uda-setter title=concept-uda-setter>common setter
-  action</a> being the same as setting the <code title=dom-location-href><a href=#dom-location-href>href</a></code> attribute to the new output
-  value.</span></p>
-<!--TOPIC:HTML-->
+  decomposition IDL attributes</a>, with the <a href=#concept-uda-input title=concept-uda-input>input</a> being <a href="#the-document's-address" title="the
+  document's address">the address</a> of the associated
+  <code><a href=#document>Document</a></code> object, as an <a href=#absolute-url>absolute URL</a> (same
+  as the <code title=dom-location-href><a href=#dom-location-href>href</a></code> attribute), and
+  the <a href=#concept-uda-setter title=concept-uda-setter>common setter action</a>
+  being the same as setting the <code title=dom-location-href><a href=#dom-location-href>href</a></code> attribute to the new output
+  value.</span></p> <!--TOPIC:HTML-->
 
 
 <!--ADD-TOPIC:Security-->
@@ -57351,10 +57402,9 @@
    these steps.</p></li>
 
    <li><p><a href=#scroll-to-the-fragment-identifier>Scroll to the fragment identifier</a> given in
-   <a href="#the-document's-current-address">the document's current address</a>. If this fails to find
-   <a href=#the-indicated-part-of-the-document title="the indicated part of the document">an indicated part
-   of the document</a>, then return to the <i>fragment identifier
-   loop</i> step.</p></li>
+   <a href="#the-document's-address">the document's address</a>. If this fails to find <a href=#the-indicated-part-of-the-document title="the indicated part of the document">an indicated part of the
+   document</a>, then return to the <i>fragment identifier loop</i>
+   step.</p></li>
 
   </ol><p>The <a href=#task-source>task source</a> for this <a href=#concept-task title=concept-task>task</a> is the <a href=#networking-task-source>networking task
   source</a>.</p>
@@ -57703,7 +57753,7 @@
 
    <li><p><a href=#traverse-the-history>Traverse the history</a> to the new entry. This
    will <a href=#scroll-to-the-fragment-identifier>scroll to the fragment identifier</a> given in what
-   is now <a href="#the-document's-current-address">the document's current address</a>.</p></li>
+   is now <a href="#the-document's-address">the document's address</a>.</p></li>
 
   </ol><p class=note>If the scrolling fails because the relevant <a href=#concept-id title=concept-id>ID</a> has not yet been parsed, then the
   original <a href=#navigate title=navigate>navigation</a> algorithm will
@@ -57886,8 +57936,8 @@
 
     </ol></li>
 
-   <li><p>Set <a href="#the-document's-current-address">the document's current address</a> to the URL
-   of the <var title="">specified entry</var>.</p></li>
+   <li><p>Set <a href="#the-document's-address">the document's address</a> to the URL of the
+   <var title="">specified entry</var>.</p></li>
 
    <li><p>If the <var title="">specified entry</var> has a URL whose
    fragment identifier differs from that of the <a href=#current-entry>current
@@ -60729,9 +60779,9 @@
     <p>A <code><a href=#document>Document</a></code> that is assigned responsibility for
     actions taken by the script.</p>
 
-    <p class=example>When a script <a href=#fetch title=fetch>fetches</a> a resource, the <a href="#the-document's-current-address" title="the
-    document's current address">current address</a> of the
-    <a href="#script's-document">script's document</a> will be used to set the <code title=http-referer>Referer</code> (sic) header.</p>
+    <p class=example>When a script <a href=#fetch title=fetch>fetches</a> a resource, the <a href="#the-document's-address" title="the
+    document's address">address</a> of the <a href="#script's-document">script's
+    document</a> will be used to set the <code title=http-referer>Referer</code> (sic) header.</p>
 
    </dd>
 
@@ -75784,9 +75834,9 @@
   <p>Once the user agent <dfn id=stop-parsing title="stop parsing">stops parsing</dfn>
   the document, the user agent must run the following steps:</p>
 
-  <ol><!-- this happens as part of one of the tasks that runs the parser --><li><p>Set the <a href=#current-document-readiness>current document readiness</a> to
-   "<code title="">interactive</code>" <!-- this also synchronously fires an event --> and
-   the <a href=#insertion-point>insertion point</a> to undefined.</p></li>
+  <ol><!-- this happens as part of one of the tasks that runs the parser --><li><p>Set the <a href=#current-document-readiness>current document readiness</a> to "<code title="">interactive</code>" <!-- this also synchronously fires an
+   event --> and the <a href=#insertion-point>insertion point</a> to
+   undefined.</p></li>
 
    <li><p>Pop <em>all</em> the nodes off the <a href=#stack-of-open-elements>stack of open
    elements</a>.</p></li>
@@ -75882,6 +75932,12 @@
    <li><p>Pop <em>all</em> the nodes off the <a href=#stack-of-open-elements>stack of open
    elements</a>.</p></li>
 
+   <li><p>Set the <a href=#current-document-readiness>current document readiness</a> to "<code title="">interactive</code>"<!-- this synchronously fires an event
+   -->.</p></li>
+
+   <li><p>Set the <a href=#current-document-readiness>current document readiness</a> to "<code title="">complete</code>"<!-- this also synchronously fires an
+   event -->.</p></li>
+
    <!-- anything else? this is things that happen when you call
    document.open() on a document that's still being parsed, or when
    you navigate a document that's still parsing, or navigate the
@@ -84681,7 +84737,7 @@
 
     </td></tr><tr><td> <code title=event-hashchange><a href=#event-hashchange>hashchange</a></code>
      </td><td> <code><a href=#hashchangeevent>HashChangeEvent</a></code>
-     </td><td> Fired at the <code><a href=#window>Window</a></code> when the fragment identifier part of <a href="#the-document's-current-address">the document's current address</a> changes
+     </td><td> Fired at the <code><a href=#window>Window</a></code> when the fragment identifier part of <a href="#the-document's-address">the document's address</a> changes
 
     </td></tr><tr><td> <code title=event-input>input</code>
      </td><td> <code><a href=#event>Event</a></code>
@@ -85782,7 +85838,7 @@
   Elliott Sprehn,
   Elliotte Harold,
   Eric Carlson,
-  Eric Law,
+  Eric Lawrence,
   Eric Rescorla,
   Eric Semling,
   Erik Arvidsson,

Index: the-end.html
===================================================================
RCS file: /sources/public/html5/spec/the-end.html,v
retrieving revision 1.165
retrieving revision 1.166
diff -u -d -r1.165 -r1.166
--- the-end.html	7 Sep 2012 00:14:03 -0000	1.165
+++ the-end.html	7 Sep 2012 11:14:07 -0000	1.166
@@ -341,9 +341,9 @@
   <p>Once the user agent <dfn id="stop-parsing" title="stop parsing">stops parsing</dfn>
   the document, the user agent must run the following steps:</p>
 
-  <ol><!-- this happens as part of one of the tasks that runs the parser --><li><p>Set the <a href="dom.html#current-document-readiness">current document readiness</a> to
-   "<code title="">interactive</code>" <!-- this also synchronously fires an event --> and
-   the <a href="parsing.html#insertion-point">insertion point</a> to undefined.</p></li>
+  <ol><!-- this happens as part of one of the tasks that runs the parser --><li><p>Set the <a href="dom.html#current-document-readiness">current document readiness</a> to "<code title="">interactive</code>" <!-- this also synchronously fires an
+   event --> and the <a href="parsing.html#insertion-point">insertion point</a> to
+   undefined.</p></li>
 
    <li><p>Pop <em>all</em> the nodes off the <a href="parsing.html#stack-of-open-elements">stack of open
    elements</a>.</p></li>
@@ -439,6 +439,12 @@
    <li><p>Pop <em>all</em> the nodes off the <a href="parsing.html#stack-of-open-elements">stack of open
    elements</a>.</p></li>
 
+   <li><p>Set the <a href="dom.html#current-document-readiness">current document readiness</a> to "<code title="">interactive</code>"<!-- this synchronously fires an event
+   -->.</p></li>
+
+   <li><p>Set the <a href="dom.html#current-document-readiness">current document readiness</a> to "<code title="">complete</code>"<!-- this also synchronously fires an
+   event -->.</p></li>
+
    <!-- anything else? this is things that happen when you call
    document.open() on a document that's still being parsed, or when
    you navigate a document that's still parsing, or navigate the

Index: constraints.html
===================================================================
RCS file: /sources/public/html5/spec/constraints.html,v
retrieving revision 1.171
retrieving revision 1.172
diff -u -d -r1.171 -r1.172
--- constraints.html	7 Sep 2012 00:13:56 -0000	1.171
+++ constraints.html	7 Sep 2012 11:14:05 -0000	1.172
@@ -818,19 +818,43 @@
   <p>If the platform supports letting the user submit a form
   implicitly (for example, on some platforms hitting the "enter" key
   while a text field is focused implicitly submits the form), then
-  doing so must cause the form's <a href="#default-button">default button</a>'s
-  <a href="content-models.html#activation-behavior">activation behavior</a>, if any, to be run.</p>
+  doing so for a form whose <a href="#default-button">default button</a> has a defined
+  <a href="content-models.html#activation-behavior">activation behavior</a> must cause the user agent to
+  <a href="content-models.html#run-synthetic-click-activation-steps">run synthetic click activation steps</a> on that
+  <a href="#default-button">default button</a>.</p>
 
   <p class="note">Consequently, if the <a href="#default-button">default button</a> is
   <a href="attributes-common-to-form-controls.html#concept-fe-disabled" title="concept-fe-disabled">disabled</a>, the form is not
   submitted when such an implicit submission mechanism is used. (A
   button has no <a href="content-models.html#activation-behavior">activation behavior</a> when disabled.)</p>
 
-  <p>If the form has no <a href="forms.html#concept-submit-button" title="concept-submit-button">submit
-  button</a>, then the implicit submission mechanism must just
+  <p><!-- For Web compatibility reasons caused by obscure historical
+  accidents, -->If the form has no <a href="forms.html#concept-submit-button" title="concept-submit-button">submit button</a>, then the
+  implicit submission mechanism must do nothing if the form has more
+  than one <i>field that blocks implicit submission</i>, and must
   <a href="#concept-form-submit" title="concept-form-submit">submit</a> the
-  <code><a href="the-form-element.html#the-form-element">form</a></code> element from the <code><a href="the-form-element.html#the-form-element">form</a></code> element
-  itself.</p>
+  <code><a href="the-form-element.html#the-form-element">form</a></code> element from the <code><a href="the-form-element.html#the-form-element">form</a></code> element itself
+  otherwise.</p>
+
+  <p>For the purpose of the previous paragraph, an element is a
+  <i>field that blocks implicit submission</i> of a <code><a href="the-form-element.html#the-form-element">form</a></code>
+  element if it is an <code><a href="the-input-element.html#the-input-element">input</a></code> element whose <a href="association-of-controls-and-forms.html#form-owner">form
+  owner</a> is that <code><a href="the-form-element.html#the-form-element">form</a></code> element and whose <code title="attr-input-type"><a href="the-input-element.html#attr-input-type">type</a></code> attribute is in one of the
+  following states:
+  <a href="states-of-the-type-attribute.html#text-(type=text)-state-and-search-state-(type=search)" title="attr-input-type-text">Text</a>,
+  <a href="states-of-the-type-attribute.html#text-(type=text)-state-and-search-state-(type=search)" title="attr-input-type-search">Search</a>,
+  <a href="states-of-the-type-attribute.html#url-state-(type=url)" title="attr-input-type-url">URL</a>,
+  <a href="states-of-the-type-attribute.html#telephone-state-(type=tel)" title="attr-input-type-tel">Telephone</a>,
+  <a href="states-of-the-type-attribute.html#e-mail-state-(type=email)" title="attr-input-type-email">E-mail</a>,
+  <a href="states-of-the-type-attribute.html#password-state-(type=password)" title="attr-input-type-password">Password</a>,
+  <a href="states-of-the-type-attribute.html#date-and-time-state-(type=datetime)" title="attr-input-type-datetime">Date and Time</a>,
+  <a href="states-of-the-type-attribute.html#date-state-(type=date)" title="attr-input-type-date">Date</a>,
+  <a href="states-of-the-type-attribute.html#month-state-(type=month)" title="attr-input-type-month">Month</a>,
+  <a href="states-of-the-type-attribute.html#week-state-(type=week)" title="attr-input-type-week">Week</a>,
+  <a href="states-of-the-type-attribute.html#time-state-(type=time)" title="attr-input-type-time">Time</a>,
+  <a href="states-of-the-type-attribute.html#local-date-and-time-state-(type=datetime-local)" title="attr-input-type-datetime-local">Local Date and Time</a>,
+  <a href="states-of-the-type-attribute.html#number-state-(type=number)" title="attr-input-type-number">Number</a>
+  </p>
 
   </div>
 

Index: webappapis.html
===================================================================
RCS file: /sources/public/html5/spec/webappapis.html,v
retrieving revision 1.375
retrieving revision 1.376
diff -u -d -r1.375 -r1.376
--- webappapis.html	7 Sep 2012 00:14:07 -0000	1.375
+++ webappapis.html	7 Sep 2012 11:14:07 -0000	1.376
@@ -498,9 +498,9 @@
     <p>A <code><a href="dom.html#document">Document</a></code> that is assigned responsibility for
     actions taken by the script.</p>
 
-    <p class="example">When a script <a href="urls.html#fetch" title="fetch">fetches</a> a resource, the <a href="dom.html#the-document's-current-address" title="the
-    document's current address">current address</a> of the
-    <a href="#script's-document">script's document</a> will be used to set the <code title="http-referer">Referer</code> (sic) header.</p>
+    <p class="example">When a script <a href="urls.html#fetch" title="fetch">fetches</a> a resource, the <a href="dom.html#the-document's-address" title="the
+    document's address">address</a> of the <a href="#script's-document">script's
+    document</a> will be used to set the <code title="http-referer">Referer</code> (sic) header.</p>
 
    </dd>
 

Index: elements.html
===================================================================
RCS file: /sources/public/html5/spec/elements.html,v
retrieving revision 1.245
retrieving revision 1.246
diff -u -d -r1.245 -r1.246
--- elements.html	7 Sep 2012 00:13:57 -0000	1.245
+++ elements.html	7 Sep 2012 11:14:05 -0000	1.246
@@ -527,8 +527,6 @@
            attribute DOMString <a href="global-attributes.html#dom-lang" title="dom-lang">lang</a>;
            attribute boolean <a href="global-attributes.html#dom-translate" title="dom-translate">translate</a>;
            attribute DOMString <a href="global-attributes.html#dom-dir" title="dom-dir">dir</a>;
-           attribute <span>DOMString</span> <a href="global-attributes.html#dom-classname" title="dom-className">className</a>;
-  readonly attribute <a href="infrastructure.html#domtokenlist">DOMTokenList</a> <a href="global-attributes.html#dom-classlist" title="dom-classList">classList</a>;
   readonly attribute <a href="common-dom-interfaces.html#domstringmap-0">DOMStringMap</a> <a href="global-attributes.html#dom-dataset" title="dom-dataset">dataset</a>;
 
 <!--MD-->
Received on Friday, 7 September 2012 11:14:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 7 September 2012 11:14:14 GMT