embed the styling processing model placeholder into the spec a bit more

git-svn-id: http://svn.whatwg.org/webapps@473 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -968,7 +968,8 @@
         maps</a>
       </ul>
 
-     <li><a href="#styling"><span class=secno>4.4. </span>Styling</a>
+     <li><a href="#styling"><span class=secno>4.4. </span><dfn id=styling0
+      title="styling processing model">Styling</dfn></a>
 
      <li><a href="#commands"><span class=secno>4.5. </span>Commands</a>
       <ul class=toc>
@@ -6968,7 +6969,9 @@ class="main"> or <div class="content">. Why do we also need a body?
   </dl>
 
   <p>The <code><a href="#style0">style</a></code> element allows authors to
-   embed style information in their documents.</p>
+   embed style information in their documents. The <code><a
+   href="#style0">style</a></code> element is one of several inputs to the <a
+   href="#styling1">styling processing model</a>.</p>
   <!-- XXX again, extract type out as a microsyntax -->
 
   <p>If the <dfn id=type1 title=attr-style-type><code>type</code></dfn>
@@ -7001,7 +7004,8 @@ class="main"> or <div class="content">. Why do we also need a body?
    title="">scoped</code>". If the attribute is present, then the user agent
    must only apply the specified style information to the <code>style<code>
    element's parent element (if any), and that element's child nodes (if
-   any), not to the rest of the document.</code></code>
+   any). Otherwise, the specified styles must be applied to the entire
+   document.</code></code>
 
   <p id=title-on-style>The <dfn id=title5
    title=attr-style-title><code>title</code></dfn> attribute on <code><a
@@ -19227,7 +19231,8 @@ mpt says:
    href="#stylesheet0">stylesheet</a></code> keyword may be used with
    <code><a href="#link0">link</a></code> elements, for which it creates an
    <a href="#links1" title="external resource link">external resource
-   link</a>.
+   link</a> that contributes to the <a href="#styling1">styling processing
+   model</a>.
 
   <p>The specified resource is a resource that describes how to present the
    document. Exactly how the resource is to be processed depends on the
@@ -19238,11 +19243,6 @@ mpt says:
    <code><a href="#link0">link</a></code> element, then the link is an
    alternate stylesheet.
 
-  <p class=big-issue>Need more here -- defining preferred stylesheets,
-   alternate stylesheets, persistent stylesheets, and the stuff about the
-   alternate stylesheet API. Maybe this should all be deferred to another
-   processing model section.
-
   <h5 id=link-type14><span class=secno>4.3.3.16. </span>Link type "<dfn
    id=sidebar0 title=rel-sidebar><code>sidebar</code></dfn>"</h5>
 
@@ -19543,9 +19543,13 @@ mpt says:
    click events clicked on areas fire directly on the area and not on the
    img?)
 
-  <h3 id=styling><span class=secno>4.4. </span>Styling</h3>
+  <h3 id=styling><span class=secno>4.4. </span><dfn id=styling1
+   title="styling processing model">Styling</dfn></h3>
 
-  <p class=big-issue>...
+  <p class=big-issue>Need more here -- defining preferred stylesheets,
+   alternate stylesheets, persistent stylesheets, ordering of stylesheets,
+   dynamic additions/removals, how it maps to .styleSheets, HTTP Link:
+   headers, and the stuff about the alternate stylesheet API.
 
   <h3 id=commands><span class=secno>4.5. </span>Commands</h3>
 

source

@@ -5743,7 +5743,9 @@ class="main"> or <div class="content">. Why do we also need a body?
   </dl>
 
   <p>The <code>style</code> element allows authors to embed style
-  information in their documents.</p>
+  information in their documents. The <code>style</code> element is
+  one of several inputs to the <span>styling processing
+  model</span>.</p>
 
   <!-- XXX again, extract type out as a microsyntax -->
   <p>If the <dfn title="attr-style-type"><code>type</code></dfn>
@@ -5777,7 +5779,8 @@ class="main"> or <div class="content">. Why do we also need a body?
   title="">scoped</code>". If the attribute is present, then the user
   agent must only apply the specified style information to the
   <code>style<code> element's parent element (if any), and that
-  element's child nodes (if any), not to the rest of the document.</p>
+  element's child nodes (if any). Otherwise, the specified styles must
+  be applied to the entire document.</p>
 
   <p id="title-on-style">The <dfn
   title="attr-style-title"><code>title</code></dfn> attribute on
@@ -17146,7 +17149,8 @@ mpt says:
 
   <p>The <code title="rel-stylesheet">stylesheet</code> keyword may be
   used with <code>link</code> elements, for which it creates an <span
-  title="external resource link">external resource link</span>.</p>
+  title="external resource link">external resource link</span> that
+  contributes to the <span>styling processing model</span>.</p>
 
   <p>The specified resource is a resource that describes how to
   present the document. Exactly how the resource is to be processed
@@ -17156,11 +17160,6 @@ mpt says:
   also specified on the <code>link</code> element, then the link is an
   alternate stylesheet.</p>
 
-  <p class="big-issue">Need more here -- defining preferred
-  stylesheets, alternate stylesheets, persistent stylesheets, and the
-  stuff about the alternate stylesheet API. Maybe this should all be
-  deferred to another processing model section.</p>
-
 
   <h5>Link type "<dfn title="rel-sidebar"><code>sidebar</code></dfn>"</h5>
 
@@ -17484,9 +17483,13 @@ mpt says:
   img?)</p>
 
 
-  <h3 id="styling">Styling</h3>
+  <h3 id="styling"><dfn title="styling processing model">Styling</dfn></h3>
 
-  <p class="big-issue">...</p>
+  <p class="big-issue">Need more here -- defining preferred
+  stylesheets, alternate stylesheets, persistent stylesheets, ordering
+  of stylesheets, dynamic additions/removals, how it maps to
+  .styleSheets, HTTP Link: headers, and the stuff about the alternate
+  stylesheet API.</p>
 
 
   <h3 id="commands">Commands</h3>