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

html5/spec association-of-controls-and-forms.html,1.56,1.57 browsers.html,1.1028,1.1029 history.html,1.1030,1.1031 offline.html,1.1017,1.1018 spec.html,1.1364,1.1365 states-of-the-type-attribute.html,1.28,1.29 tokenization.html,1.56,1.57 webappapis.html,1.150,1.151

From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 11 Jan 2011 01:23:57 +0000
To: public-html-commits@w3.org
Message-Id: <E1PcSxq-0005tq-0z@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv22658

Modified Files:
	association-of-controls-and-forms.html browsers.html 
	history.html offline.html spec.html 
	states-of-the-type-attribute.html tokenization.html 
	webappapis.html 
Log Message:
typos (whatwg r5762)

[updated by splitter]


Index: association-of-controls-and-forms.html
===================================================================
RCS file: /sources/public/html5/spec/association-of-controls-and-forms.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- association-of-controls-and-forms.html	10 Jan 2011 12:35:12 -0000	1.56
+++ association-of-controls-and-forms.html	11 Jan 2011 01:23:54 -0000	1.57
@@ -584,10 +584,10 @@
   <ol><li><p>Let <var title="">target</var> be the element's
    <code><a href="infrastructure.html#document">Document</a></code>.</p></li>
 
-   <li><p>Let <var title="">target</var> has no <a href="browsers.html#browsing-context">browsing
+   <li><p>If <var title="">target</var> has no <a href="browsers.html#browsing-context">browsing
    context</a>, abort these steps.</p></li>
 
-   <li><p>Let <var title="">target</var>'s <a href="browsers.html#browsing-context">browsing
+   <li><p>If <var title="">target</var>'s <a href="browsers.html#browsing-context">browsing
    context</a> has no <a href="browsers.html#top-level-browsing-context">top-level browsing context</a> (e.g.
    it is a <a href="browsers.html#nested-browsing-context">nested browsing context</a> with no <a href="browsers.html#parent-browsing-context">parent
    browsing context</a>), abort these steps.</p></li>

Index: history.html
===================================================================
RCS file: /sources/public/html5/spec/history.html,v
retrieving revision 1.1030
retrieving revision 1.1031
diff -u -d -r1.1030 -r1.1031
--- history.html	10 Jan 2011 12:35:14 -0000	1.1030
+++ history.html	11 Jan 2011 01:23:54 -0000	1.1031
@@ -595,15 +595,24 @@
    <a href="browsers.html#browsing-context">browsing context</a> of the <var title="">specified
    entry</var>.</p></li>
 
-   <li><p><a href="#prompt-to-unload-a-document" title="prompt to unload a document">Prompt to
-   unload</a> the <a href="browsers.html#active-document">active document</a> of the <var title="">specified browsing context</var>. If the user
-   <a href="#refused-to-allow-the-document-to-be-unloaded">refused to allow the document to be unloaded</a>, then
-   abort these steps.</p></li>
+   <li>
 
-   <li><p><a href="#unload-a-document" title="unload a document">Unload</a> the
-   <a href="browsers.html#active-document">active document</a> of the <var title="">specified
-   browsing context</var> with the <var title="">recycle</var>
-   parameter set to false.</p></li>
+    <p>If the <var title="">specified browsing context</var>'s
+    <a href="browsers.html#active-document">active document</a> is not the same <code><a href="infrastructure.html#document">Document</a></code>
+    as the <code><a href="infrastructure.html#document">Document</a></code> of the <var title="">specified
+    entry</var>, then run these substeps:</p>
+
+    <ol><li><p><a href="#prompt-to-unload-a-document" title="prompt to unload a document">Prompt to
+     unload</a> the <a href="browsers.html#active-document">active document</a> of the <var title="">specified browsing context</var>. If the user
+     <a href="#refused-to-allow-the-document-to-be-unloaded">refused to allow the document to be unloaded</a>, then
+     abort these steps.</p></li>
+
+     <li><p><a href="#unload-a-document" title="unload a document">Unload</a> the
+     <a href="browsers.html#active-document">active document</a> of the <var title="">specified
+     browsing context</var> with the <var title="">recycle</var>
+     parameter set to false.</p></li>
+
+    </ol></li>
 
    <li><p><a href="#traverse-the-history">Traverse the history</a> of the <var title="">specified browsing context</var> to the <var title="">specified entry</var>.</p>
 

Index: tokenization.html
===================================================================
RCS file: /sources/public/html5/spec/tokenization.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- tokenization.html	31 Dec 2010 04:46:53 -0000	1.56
+++ tokenization.html	11 Jan 2011 01:23:55 -0000	1.57
@@ -5148,7 +5148,15 @@
   mode: in table text">in table text</a>", tokens must be handled
   as follows:</p>
 
-  <dl class="switch"><dt>A character token</dt>
+  <dl class="switch"><dt>A character token that is U+0000 NULL</dt>
+   <dd>
+
+    <p><a href="parsing.html#parse-error">Parse error</a>. Ignore the token.</p>
+
+   </dd>
+
+
+   <dt>Any other character token</dt>
    <dd>
 
     <p>Append the character token to the <var><a href="#pending-table-character-tokens">pending table character
@@ -5163,10 +5171,10 @@
     <p>If any of the tokens in the <var><a href="#pending-table-character-tokens">pending table character
     tokens</a></var> list are character tokens that are not one of U+0009
     CHARACTER TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED
-    (FF), U+000D CARRIAGE RETURN (CR), or U+0020 SPACE, then
-    reprocess those character tokens using the rules given in the
-    "anything else" entry in the <a href="#parsing-main-intable" title="insertion mode: in
-    table">in table</a>" insertion mode.</p>
+    (FF), U+000D CARRIAGE RETURN (CR), or U+0020 SPACE, then reprocess
+    those character tokens using the rules given in the "anything
+    else" entry in the <a href="#parsing-main-intable" title="insertion mode: in table">in
+    table</a>" insertion mode.</p>
 
     <p>Otherwise, <a href="#insert-a-character" title="insert a character">insert the
     characters</a> given by the <var><a href="#pending-table-character-tokens">pending table character

Index: browsers.html
===================================================================
RCS file: /sources/public/html5/spec/browsers.html,v
retrieving revision 1.1028
retrieving revision 1.1029
diff -u -d -r1.1028 -r1.1029
--- browsers.html	1 Jan 2011 06:46:39 -0000	1.1028
+++ browsers.html	11 Jan 2011 01:23:54 -0000	1.1029
@@ -478,14 +478,22 @@
   <code><a href="infrastructure.html#document">Document</a></code> <var title="">d</var> is the (ordered) list
   returned by the following algorithm:</p><ol><li><p>Let <var title="">list</var> be an empty list.</p></li>
 
-   <li><p>For each <a href="#child-browsing-context">child browsing context</a> of <var title="">d</var> that is <a href="#browsing-context-nested-through" title="browsing context nested
-   through">nested through</a> an element that is <a href="infrastructure.html#in-a-document" title="in a
-   document">in the <code>Document</code></a> <var title="">d</var>, in the <a href="infrastructure.html#tree-order">tree order</a> of the elements
-   nesting those <a href="#browsing-context" title="browsing context">browsing
-   contexts</a>, append to the list <var title="">list</var> the
-   <a href="#list-of-the-descendant-browsing-contexts">list of the descendant browsing contexts</a> of the
-   <a href="#active-document">active document</a> of that <a href="#child-browsing-context">child browsing
-   context</a>.</p></li>
+   <li>
+
+    <p>For each <a href="#child-browsing-context">child browsing context</a> of <var title="">d</var> that is <a href="#browsing-context-nested-through" title="browsing context nested
+    through">nested through</a> an element that is <a href="infrastructure.html#in-a-document" title="in
+    a document">in the <code>Document</code></a> <var title="">d</var>, in the <a href="infrastructure.html#tree-order">tree order</a> of the elements
+    nesting those <a href="#browsing-context" title="browsing context">browsing
+    contexts</a>, run these substeps:</p>
+
+    <ol><li><p>Append that <a href="#child-browsing-context">child browsing context</a> to the
+     list <var title="">list</var>.</p>
+
+     </li><li><p>Append the <a href="#list-of-the-descendant-browsing-contexts">list of the descendant browsing
+     contexts</a> of the <a href="#active-document">active document</a> of that
+     <a href="#child-browsing-context">child browsing context</a> to the list <var title="">list</var>.</p></li>
+
+    </ol></li>
 
    <li><p>Return the constructed <var title="">list</var>.</p></li>
 
@@ -700,12 +708,17 @@
   context name</dfn> are as follows. The rules assume that they are
   being applied in the context of a <a href="#browsing-context">browsing context</a>.</p>
 
-  <ol><li><p>If the given browsing context name is the empty string or
-   <code title="">_self</code>, then the chosen browsing context must
-   be the current one. This is an <dfn id="explicit-self-navigation-override">explicit self-navigation
-   override</dfn>, which overrides the behavior of the <a href="the-iframe-element.html#seamless-browsing-context-flag">seamless
-   browsing context flag</a> set by the <code title="attr-iframe-seamless"><a href="the-iframe-element.html#attr-iframe-seamless">seamless</a></code> attribute on
-   <code><a href="the-iframe-element.html#the-iframe-element">iframe</a></code> elements.</p></li>
+  <ol><li>
+
+    <p>If the given browsing context name is the empty string or <code title="">_self</code>, then the chosen browsing context must be
+    the current one.</p>
+
+    <p>If the given browsing context name is <code title="">_self</code>, then this is an <dfn id="explicit-self-navigation-override">explicit
+    self-navigation override</dfn>, which overrides the behavior of
+    the <a href="the-iframe-element.html#seamless-browsing-context-flag">seamless browsing context flag</a> set by the <code title="attr-iframe-seamless"><a href="the-iframe-element.html#attr-iframe-seamless">seamless</a></code> attribute on
+    <code><a href="the-iframe-element.html#the-iframe-element">iframe</a></code> elements.</p>
+
+   </li>
 
    <li><p>If the given browsing context name is <code title="">_parent</code>, then the chosen browsing context must be
    the <a href="#parent-browsing-context"><em>parent</em> browsing context</a> of the current

Index: offline.html
===================================================================
RCS file: /sources/public/html5/spec/offline.html,v
retrieving revision 1.1017
retrieving revision 1.1018
diff -u -d -r1.1017 -r1.1018
--- offline.html	14 Dec 2010 02:46:43 -0000	1.1017
+++ offline.html	11 Jan 2011 01:23:54 -0000	1.1018
@@ -2071,23 +2071,49 @@
   primed the first time), making the testing of offline applications
   simpler.</p>
 
-  </div><h4 id="expiring-application-caches"><span class="secno">5.6.7 </span>Expiring application caches</h4><p>As a general rule, user agents should not expire application
+  </div><div class="impl">
+
+  <h4 id="expiring-application-caches"><span class="secno">5.6.7 </span>Expiring application caches</h4>
+
+  <p>As a general rule, user agents should not expire application
   caches, except on request from the user, or after having been left
-  unused for an extended period of time.</p><p>Application caches and cookies have similar implications with
+  unused for an extended period of time.</p>
+
+  <p>Application caches and cookies have similar implications with
   respect to privacy (e.g. if the site can identify the user when
   providing the cache, it can store data in the cache that can be used
   for cookie resurrection). Implementors are therefore encouraged to
   expose application caches in a manner related to HTTP cookies,
   allowing caches to be expunged together with cookies and other
-  origin-specific data.</p><p class="example">For example, a user agent could have a "delete
+  origin-specific data.</p>
+
+  <p class="example">For example, a user agent could have a "delete
   site-specific data" feature that clears all cookies, application
   caches, local storage, databases, etc, from an origin all at
-  once.</p><h4 id="disk-space"><span class="secno">5.6.8 </span>Disk space</h4><p>User agents should consider applying constraints on disk usage of
+  once.</p>
+
+  </div><div class="impl">
+
+  <h4 id="disk-space"><span class="secno">5.6.8 </span>Disk space</h4>
+
+  <p>User agents should consider applying constraints on disk usage of
   <a href="#application-cache" title="application cache">application caches</a>, and care
   should be taken to ensure that the restrictions cannot be easily
-  worked around using subdomains.</p><p>User agents should allow users to see how much space each domain
+  worked around using subdomains.</p>
+
+  <p>User agents should allow users to see how much space each domain
   is using, and may offer the user the ability to delete specific
-  <a href="#application-cache" title="application cache">application caches</a>.</p><h4 id="application-cache-api"><span class="secno">5.6.9 </span>Application cache API</h4><pre class="idl">interface <dfn id="applicationcache">ApplicationCache</dfn> {
+  <a href="#application-cache" title="application cache">application caches</a>.</p>
+
+  <p class="note">How quotas are presented to the user is not defined
+  by this specification. User agents are encouraged to provide
+  features such as allowing a user to indicate that certain sites are
+  trusted to use more than the default quota, e.g. by asynchronously
+  presenting a user interface while a cache is being updated, or by
+  having an explicit whitelist in the user agent's configuration
+  interface.</p>
+
+  </div><h4 id="application-cache-api"><span class="secno">5.6.9 </span>Application cache API</h4><pre class="idl">interface <dfn id="applicationcache">ApplicationCache</dfn> {
 
   // <a href="#concept-appcache-status" title="concept-appcache-status">update status</a>
   const unsigned short <a href="#dom-appcache-uncached" title="dom-appcache-UNCACHED">UNCACHED</a> = 0;

Index: states-of-the-type-attribute.html
===================================================================
RCS file: /sources/public/html5/spec/states-of-the-type-attribute.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -d -r1.28 -r1.29
--- states-of-the-type-attribute.html	10 Jan 2011 12:35:15 -0000	1.28
+++ states-of-the-type-attribute.html	11 Jan 2011 01:23:55 -0000	1.29
@@ -1056,7 +1056,10 @@
   global date and time string</a> expressed in UTC representing the
   user's selection. User agents should allow the user to set the <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a> to the empty string.</p>
 
-  </div><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
+  </div><p class="note">The format shown to the user is independent of the
+  format used for form submission. Browsers are encouraged to use user
+  interfaces that present dates and times according to the conventions
+  of the user's preferred locale.</p><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
   specified, must have a value that is a <a href="common-microsyntaxes.html#valid-global-date-and-time-string">valid global date and
   time string</a>.</p><!-- ok to set out-of-range value, we never
   know when we might have to represent bogus input --><div class="impl">
@@ -1202,7 +1205,10 @@
   date string</a> representing the user's selection. User agents
   should allow the user to set the <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a> to the empty string.</p>
 
-  </div><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
+  </div><p class="note">The format shown to the user is independent of the
+  format used for form submission. Browsers are encouraged to use user
+  interfaces that present dates according to the conventions of the
+  user's preferred locale.</p><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
   specified, must have a value that is a <a href="common-microsyntaxes.html#valid-date-string">valid date
   string</a>.</p><!-- ok to set out-of-range value, we never know
   when we might have to represent bogus input --><div class="impl">
@@ -1328,7 +1334,10 @@
   month string</a> representing the user's selection. User agents
   should allow the user to set the <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a> to the empty string.</p>
 
-  </div><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
+  </div><p class="note">The format shown to the user is independent of the
+  format used for form submission. Browsers are encouraged to use user
+  interfaces that present months according to the conventions of the
+  user's preferred locale.</p><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
   specified, must have a value that is a <a href="common-microsyntaxes.html#valid-month-string">valid month
   string</a>.</p><!-- ok to set out-of-range value, we never know
   when we might have to represent bogus input --><div class="impl">
@@ -1455,7 +1464,10 @@
   week string</a> representing the user's selection. User agents
   should allow the user to set the <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a> to the empty string.</p>
 
-  </div><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
+  </div><p class="note">The format shown to the user is independent of the
+  format used for form submission. Browsers are encouraged to use user
+  interfaces that present weeks according to the conventions of the
+  user's preferred locale.</p><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
   specified, must have a value that is a <a href="common-microsyntaxes.html#valid-week-string">valid week
   string</a>.</p><!-- ok to set out-of-range value, we never know
   when we might have to represent bogus input --><div class="impl">
@@ -1585,7 +1597,10 @@
   time string</a> representing the user's selection. User agents
   should allow the user to set the <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a> to the empty string.</p>
 
-  </div><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
+  </div><p class="note">The format shown to the user is independent of the
+  format used for form submission. Browsers are encouraged to use user
+  interfaces that present times according to the conventions of the
+  user's preferred locale.</p><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
   specified, must have a value that is a <a href="common-microsyntaxes.html#valid-time-string">valid time
   string</a>.</p><!-- ok to set out-of-range value, we never know
   when we might have to represent bogus input --><div class="impl">
@@ -1711,7 +1726,10 @@
   <a href="common-microsyntaxes.html#valid-local-date-and-time-string">valid local date and time string</a> representing the
   user's selection. User agents should allow the user to set the <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a> to the empty string.</p>
 
-  </div><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
+  </div><p class="note">The format shown to the user is independent of the
+  format used for form submission. Browsers are encouraged to use user
+  interfaces that present dates and times according to the conventions
+  of the user's preferred locale.</p><p>The <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, if
   specified, must have a value that is a <a href="common-microsyntaxes.html#valid-local-date-and-time-string">valid local date and
   time string</a>.</p><!-- ok to set out-of-range value, we never
   know when we might have to represent bogus input --><div class="impl">

Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec/spec.html,v
retrieving revision 1.1364
retrieving revision 1.1365
diff -u -d -r1.1364 -r1.1365
--- spec.html	10 Jan 2011 12:35:15 -0000	1.1364
+++ spec.html	11 Jan 2011 01:23:55 -0000	1.1365
@@ -388,7 +388,7 @@
     <a href="Overview.html">single page HTML</a>,
     <a href="spec.html">multipage HTML</a>,
     <a href="author/">web developer edition</a>.
-This is revision 1.4615.
+This is revision 1.4624.
    </p> 
      <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
    &#169; 2010 <a href="http://www.w3.org/"><abbr title="World Wide
@@ -424,7 +424,7 @@
   public bug database</a>. If you do not have an account then you can
   enter feedback using this form:</p><form action="http://www.whatwg.org/specs/web-apps/current-work/file-spam.cgi" method="post">
    <fieldset><legend>Feedback Comments</legend>
-    <input name="id" type="hidden" value="top"><input name="component" type="hidden" value="HTML Canvas 2D Context (editor: Ian Hickson)"><input name="response" type="hidden" value="html"><p><label for="feedbackBox">Please enter your feedback, carefully
+    <input name="id" type="hidden" value="top"><input name="component" type="hidden" value="HTML5 spec (editor: Ian Hickson)"><input name="response" type="hidden" value="html"><p><label for="feedbackBox">Please enter your feedback, carefully
     indicating the title of the section for which you are submitting
     feedback, quoting the text that's wrong today if appropriate. If
     you're suggesting a new feature, it's really important to say

Index: webappapis.html
===================================================================
RCS file: /sources/public/html5/spec/webappapis.html,v
retrieving revision 1.150
retrieving revision 1.151
diff -u -d -r1.150 -r1.151
--- webappapis.html	1 Jan 2011 06:46:43 -0000	1.150
+++ webappapis.html	11 Jan 2011 01:23:55 -0000	1.151
@@ -978,6 +978,16 @@
     <p>Use the appropriate step from the following list:</p>
 
     <dl><dt>If a <a href="browsers.html#browsing-context">browsing context</a> is being <a href="history.html#navigate" title="navigate">navigated</a> to a <code>javascript:</code>
+     URL, and the <a href="history.html#source-browsing-context">source browsing context</a> for that
+     navigation, if any, has <a href="#concept-bc-noscript" title="concept-bc-noscript">scripting disabled</a></dt>
+
+     <dd>
+
+      <p>Let <var title="">result</var> be void.</p>
+
+     </dd>
+
+     <dt>If a <a href="browsers.html#browsing-context">browsing context</a> is being <a href="history.html#navigate" title="navigate">navigated</a> to a <code>javascript:</code>
      URL, and the <a href="browsers.html#active-document">active document</a> of that browsing
      context has the <a href="origin-0.html#same-origin">same origin</a> as the script given by
      that URL</dt>
Received on Tuesday, 11 January 2011 01:24:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 01:24:02 GMT