[html5] r1135 - /

whatwg at whatwg.org whatwg at whatwg.org
Mon Nov 12 20:49:46 PST 2007


Author: ianh
Date: 2007-11-12 20:49:44 -0800 (Mon, 12 Nov 2007)
New Revision: 1135

Modified:
   index
   source
Log:
[e] (0) minor pubrules fixes

Modified: index
===================================================================
--- index	2007-11-08 23:06:59 UTC (rev 1134)
+++ index	2007-11-13 04:49:44 UTC (rev 1135)
@@ -22,7 +22,8 @@
 
    <h1 id=html-5>HTML 5</h1>
 
-   <h2 class="no-num no-toc" id=working>Working Draft — 8 November 2007</h2>
+   <h2 class="no-num no-toc" id=working>Working Draft — 13 November
+    2007</h2>
 
    <p>You can take part in this work. <a
     href="http://www.whatwg.org/mailing-list">Join the working group's
@@ -1661,12 +1662,6 @@
 
    <li><a href="#rendering"><span class=secno>10. </span>Rendering</a>
     <ul class=toc>
-     <li>
-      <ul class=toc>
-       <li><a href="#section"><span class=secno>10.0.1. </span>Section
-        headers</a>
-      </ul>
-
      <li><a href="#rendering0"><span class=secno>10.1. </span>Rendering and
       the DOM</a>
 
@@ -5977,7 +5972,7 @@
   <ul>
    <li>Some can only contain other block-level elements: <code><a
     href="#blockquote">blockquote</a></code>, <code><a
-    href="#section0">section</a></code>, <code><a
+    href="#section">section</a></code>, <code><a
     href="#article">article</a></code>, <code><a
     href="#header">header</a></code>.
 
@@ -7877,7 +7872,7 @@
     href="#scoped">scoped</a></code> attribute is present: at the start of
     <code><a href="#article">article</a></code>, <code><a
     href="#aside">aside</a></code>, <code><a href="#div">div</a></code>, and
-    <code><a href="#section0">section</a></code> elements.
+    <code><a href="#section">section</a></code> elements.
 
    <dt>Content model:
 
@@ -7957,9 +7952,9 @@
    href="#style">style</a></code> element must be the child of an <code><a
    href="#article">article</a></code>, <code><a
    href="#aside">aside</a></code>, <code><a href="#div">div</a></code>, or
-   <code><a href="#section0">section</a></code> element, before any text
-   nodes other than <a href="#inter-element">inter-element whitespace</a>,
-   and before any elements other than other <code><a
+   <code><a href="#section">section</a></code> element, before any text nodes
+   other than <a href="#inter-element">inter-element whitespace</a>, and
+   before any elements other than other <code><a
    href="#style">style</a></code> elements.
 
   <p id=title-on-style>The <dfn id=title3
@@ -8155,7 +8150,7 @@
    arbitrary <code><a href="#body0">body</a></code> element.
 
   <h4 id=the-section><span class=secno>3.8.2. </span>The <dfn
-   id=section0><code>section</code></dfn> element</h4>
+   id=section><code>section</code></dfn> element</h4>
 
   <p><a href="#sectioning" title="sectioning elements">Sectioning</a> <a
    href="#block-level0" title="block-level elements">block-level element</a>.
@@ -8181,7 +8176,7 @@
     href="#htmlelement">HTMLElement</a></code>.
   </dl>
 
-  <p>The <code><a href="#section0">section</a></code> element represents a
+  <p>The <code><a href="#section">section</a></code> element represents a
    generic document or application section. A section, in this context, is a
    thematic grouping of content, typically with a header, possibly with a
    footer.
@@ -8191,8 +8186,8 @@
    site's home page could be split into sections for an introduction, news
    items, contact information.
 
-  <p>Each <code><a href="#section0">section</a></code> element potentially
-   has a heading. See the section on <a href="#headings0">headings and
+  <p>Each <code><a href="#section">section</a></code> element potentially has
+   a heading. See the section on <a href="#headings0">headings and
    sections</a> for further details.
 
   <h4 id=the-nav><span class=secno>3.8.3. </span>The <dfn
@@ -8488,7 +8483,7 @@
   <p><code><a href="#header">header</a></code> elements must not contain any
    <code><a href="#header">header</a></code> elements, <code><a
    href="#footer">footer</a></code> elements, or any sectioning elements
-   (such as <code><a href="#section0">section</a></code>) as descendants.
+   (such as <code><a href="#section">section</a></code>) as descendants.
 
   <p><code><a href="#header">header</a></code> elements must have at least
    one <code><a href="#h1">h1</a></code>, <code><a href="#h2">h2</a></code>,
@@ -8593,7 +8588,7 @@
    <code><a href="#h2">h2</a></code>, <code><a href="#h3">h3</a></code>,
    <code><a href="#h4">h4</a></code>, <code><a href="#h5">h5</a></code>, or
    <code><a href="#h6">h6</a></code> elements, or any of the sectioning
-   elements (such as <code><a href="#section0">section</a></code>), as
+   elements (such as <code><a href="#section">section</a></code>), as
    descendants.
 
   <p>When <a href="#determining1" title="Determining if a particular element
@@ -8732,14 +8727,14 @@
       <li> Quux (heading starting implied section)
 
       <li> Thud (heading of explicit <code><a
-       href="#section0">section</a></code> section)
+       href="#section">section</a></code> section)
      </ol>
      Grunt (paragraph)
    </ol>
 
    <p>Notice how the <code><a href="#blockquote">blockquote</a></code> nests
     inside an implicit section while the <code><a
-    href="#section0">section</a></code> does not (and in fact, ends the
+    href="#section">section</a></code> does not (and in fact, ends the
     earlier implicit section so that a later paragraph is back at the top
     level).</p>
   </div>
@@ -26293,8 +26288,8 @@
    <dfn id=update0 title=concept-appcache-status>update status</dfn>, which
    is one of the following: <i>idle</i>, <i>checking</i>, <i>downloading</i>.
 
-  <p id="#appcache-history-1">A <a href="#browsing0">browsing context</a> can
-   be associated with an application cache. A <a href="#child">child browsing
+  <p id=appcache-history-1>A <a href="#browsing0">browsing context</a> can be
+   associated with an application cache. A <a href="#child">child browsing
    context</a> is always associated with the same browsing context as its <a
    href="#parent">parent browsing context</a>, if any. A <a
    href="#top-level">top-level browsing context</a> is associated with the
@@ -31242,11 +31237,12 @@
    request, and is independent of the result of that request.
 
   <p>User agents should allow the user to adjust this behaviour, for example
-   in conjunction with a setting that disables the sending of HTTP <coe
-   title="">Referer headers. Based on the user's preferences, UAs may either
-   <a href="#ignored">ignore</a> the <code title=attr-hyperlink-ping><a
-   href="#ping">ping</a></code> attribute altogether, or selectively ignore
-   URIs in the list (e.g. ignoring any third-party URIs).</coe>
+   in conjunction with a setting that disables the sending of HTTP <code
+   title="">Referer</code> headers. Based on the user's preferences, UAs may
+   either <a href="#ignored">ignore</a> the <code
+   title=attr-hyperlink-ping><a href="#ping">ping</a></code> attribute
+   altogether, or selectively ignore URIs in the list (e.g. ignoring any
+   third-party URIs).
 
   <p>For URIs that are HTTP URIs, the requests must be performed using the
    POST method (with an empty entity body in the request). User agents must
@@ -32719,7 +32715,7 @@
      <p>...the user agent should allow the user to insert <code><a
       href="#p">p</a></code> elements before and after the <code><a
       href="#dl">dl</a></code> element, as children of the <code><a
-      href="#section0">section</a></code> element.</p>
+      href="#section">section</a></code> element.</p>
     </div>
 
    <dt id=contenteditable-breakBlock>Break block
@@ -39967,7 +39963,7 @@
 
   <p class=big-issue>Still need to add these new elements to the lists:
    <code><a href="#event-source">event-source</a></code>, <code><a
-   href="#section0">section</a></code>, <code><a href="#nav">nav</a></code>,
+   href="#section">section</a></code>, <code><a href="#nav">nav</a></code>,
    <code><a href="#article">article</a></code>, <code><a
    href="#aside">aside</a></code>, <code><a href="#header">header</a></code>,
    <code><a href="#footer">footer</a></code>, <code><a
@@ -45164,20 +45160,18 @@
 
   <pre>@namespace xh url(http://www.w3.org/1999/xhtml);
 xh|section { display: block; margin: 1em 0; }</pre>
-
-
-<!-- XXX alt="": Define that either the src="" is shown (as an image)
+-->
+  <!-- XXX alt="": Define that either the src="" is shown (as an image)
 or the alt="" is shown (inline) but should not ever have both at
 once. -->
+  <!--
+  <h4>Section headers</h4>
 
-  <h4 id=section><span class=secno>10.0.1. </span>Section headers</h4>
+  <p>For <code>h1</code> elements, CSS-aware visual user agents should
+  derive the size of the header from the level of <code>section</code>
+  nesting. This effect should be achieved by including the following
+  rules, or their equivalent, in the UA's user agent style sheet:</p>
 
-  <p>For <code><a href="#h1">h1</a></code> elements, CSS-aware visual user
-   agents should derive the size of the header from the level of <code><a
-   href="#section0">section</a></code> nesting. This effect should be
-   achieved by including the following rules, or their equivalent, in the
-   UA's user agent style sheet:
-
   <pre>@namespace xh url(http://www.w3.org/1999/xhtml);
 xh|section xh|h1 { /* same styles as h2 */ }
 xh|section xh|section xh|h1 { /* same styles as h4 */ }
@@ -45185,13 +45179,12 @@
 xh|section xh|section xh|section xh|section xh|h1 { /* same styles as h5 */ }
 xh|section xh|section xh|section xh|section xh|section xh|h1 { /* same styles as h6 */ }</pre>
 
-  <p>Authors should use <code><a href="#h1">h1</a></code> elements to denote
-   headers in sections. Authors may instead use <code><a
-   href="#h2">h2</a></code> ... <code><a href="#h6">h6</a></code> elements,
-   for backwards compatibility with user agents that do not support <code><a
-   href="#section0">section</a></code> elements.
+  <p>Authors should use <code>h1</code> elements to denote headers in
+  sections. Authors may instead use <code>h2</code> ...
+  <code>h6</code> elements, for backwards compatibility with user
+  agents that do not support <code>section</code> elements.</p>
 
-  <p>-->
+-->
 
   <p class=big-issue> must define letting the user <dfn id=obtain>obtain a
    physical form</dfn> of a document (printing) and what this means for the

Modified: source
===================================================================
--- source	2007-11-08 23:06:59 UTC (rev 1134)
+++ source	2007-11-13 04:49:44 UTC (rev 1135)
@@ -23857,7 +23857,7 @@
   which is one of the following: <i>idle</i>, <i>checking</i>,
   <i>downloading</i>.</p>
 
-  <p id="#appcache-history-1">A <span>browsing context</span> can be
+  <p id="appcache-history-1">A <span>browsing context</span> can be
   associated with an application cache. A <span>child browsing
   context</span> is always associated with the same browsing context
   as its <span>parent browsing context</span>, if any. A
@@ -28812,7 +28812,7 @@
 
   <p>User agents should allow the user to adjust this behaviour, for
   example in conjunction with a setting that disables the sending of
-  HTTP <coe title="">Referer</code> headers. Based on the user's
+  HTTP <code title="">Referer</code> headers. Based on the user's
   preferences, UAs may either <span>ignore</span> the <code
   title="attr-hyperlink-ping">ping</code> attribute altogether, or
   selectively ignore URIs in the list (e.g. ignoring any third-party
@@ -40999,12 +40999,14 @@
 
   <pre>@namespace xh url(http://www.w3.org/1999/xhtml);
 xh|section { display: block; margin: 1em 0; }</pre>
+-->
 
 
 <!-- XXX alt="": Define that either the src="" is shown (as an image)
 or the alt="" is shown (inline) but should not ever have both at
 once. -->
 
+<!--
   <h4>Section headers</h4>
 
   <p>For <code>h1</code> elements, CSS-aware visual user agents should




More information about the Commit-Watchers mailing list