[] (0) Filling in the rendering section: <mark>, links.

git-svn-id: http://svn.whatwg.org/webapps@2770 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Feb 10, 2009 · 94f624a · 94f624a
1 parent f90a23d
commit 94f624a
Show file tree

Hide file tree

Showing 2 changed files with 61 additions and 54 deletions.
diff --git a/index b/index
@@ -1069,10 +1069,9 @@
    <li><a href=#interactive-media><span class=secno>10.6 </span>Interactive media</a>
     <ol>
      <li><a href=#hit-testing><span class=secno>10.6.1 </span>Hit testing</a></li>
-     <li><a href=#links-0><span class=secno>10.6.2 </span>Links</a></li>
+     <li><a href=#links,-forms,-and-navigation><span class=secno>10.6.2 </span>Links, forms, and navigation</a></li>
      <li><a href=#the-mark-element-0><span class=secno>10.6.3 </span>The <code>mark</code> element</a></li>
-     <li><a href=#the-contenteditable-attribute><span class=secno>10.6.4 </span>The <code title=attr-contenteditable>contenteditable</code> attribute</a></li>
-     <li><a href=#the-title-attribute-0><span class=secno>10.6.5 </span>The <code title=attr-title>title</code> attribute</a></ol></li>
+     <li><a href=#the-title-attribute-0><span class=secno>10.6.4 </span>The <code title=attr-title>title</code> attribute</a></ol></li>
    <li><a href=#print-media><span class=secno>10.7 </span>Print media</a></li>
    <li><a href=#interaction-with-css><span class=secno>10.8 </span>Interaction with CSS</a></ol></li>
  <li><a href=#obsolete-features><span class=secno>11 </span>Obsolete features</a>
@@ -10456,9 +10455,9 @@ not-slash     = %x0000-002E / %x0030-%10FFFF
 
   <p>The <code><a href=#the-noscript-element>noscript</a></code> element has no other requirements. In
   particular, children of the <code><a href=#the-noscript-element>noscript</a></code> element are not
-  exempt from form submission, scripting, and so forth, even when
-  <a href=#concept-n-script title=concept-n-script>scripting is enabled</a> for the
-  element.</p>
+  exempt from <a href=#form-submission-0>form submission</a>, scripting, and so forth,
+  even when <a href=#concept-n-script title=concept-n-script>scripting is enabled</a>
+  for the element.</p>
 
 
 
@@ -24107,7 +24106,8 @@ function AddCloud(data, x, y) { ... }</pre>
 
   <p class=note>The <code><a href=#the-object-element>object</a></code> element is also a
   <a href=#form-associated-element>form-associated element</a> and can, with the use of a
-  suitable <a href=#plugin>plugin</a>, partake in form submission.</p>
+  suitable <a href=#plugin>plugin</a>, partake in <a href=#form-submission-0>form
+  submission</a>.</p>
 
 
   <h4 id=the-form-element><span class=secno>4.10.1 </span>The <dfn><code>form</code></dfn> element</h4>
@@ -29408,8 +29408,8 @@ interface <dfn id=htmloptionelement>HTMLOptionElement</dfn> : <a href=#htmleleme
   <h5 id=naming-form-controls><span class=secno>4.10.13.1 </span>Naming form controls</h5>
 
   <p>The <dfn id=attr-fe-name title=attr-fe-name><code>name</code></dfn> content
-  attribute gives the name of the form control, as used in form
-  submission and in the <code><a href=#the-form-element>form</a></code> element's <code title=dom-form-elements><a href=#dom-form-elements>elements</a></code> object. If the attribute
+  attribute gives the name of the form control, as used in <a href=#form-submission-0>form
+  submission</a> and in the <code><a href=#the-form-element>form</a></code> element's <code title=dom-form-elements><a href=#dom-form-elements>elements</a></code> object. If the attribute
   is specified, its value must not be the empty string.</p>
 
   <p><strong>Constraint validation:</strong> If an element does not
@@ -29871,7 +29871,7 @@ interface <dfn id=htmloptionelement>HTMLOptionElement</dfn> : <a href=#htmleleme
 
 
 
-  <h4 id=form-submission-0><span class=secno>4.10.15 </span>Form submission</h4>
+  <h4 id=form-submission-0><span class=secno>4.10.15 </span><dfn>Form submission</dfn></h4>
 
   <h5 id=implicit-submission><span class=secno>4.10.15.1 </span>Implicit submission</h5>
 
@@ -57911,35 +57911,37 @@ target element as follows:
 
 
 
-  <h4 id=links-0><span class=secno>10.6.2 </span>Links</h4>
-
-  <p class=XXX>...</p>
-  <!-- hyperlinks: hover show url; clicks; opening in new browsing contexts -->
-  <!-- cite attribute on q, blockquote, ins, del: on hover, show link -->
-
-
+  <h4 id=links,-forms,-and-navigation><span class=secno>10.6.2 </span>Links, forms, and navigation</h4>
 
-  <h4 id=the-mark-element-0><span class=secno>10.6.3 </span>The <code><a href=#the-mark-element>mark</a></code> element</h4>
+  <p>User agents are expected to allow the user to control aspects of
+  <a href=#hyperlink>hyperlink</a> activation and <a href=#form-submission-0>form submission</a>,
+  such as which <a href=#browsing-context>browsing context</a> is to be used for the
+  subsequent <a href=#navigate title=navigate>navigation</a>.</p>
 
-  <p class=XXX>...</p>
-  <!-- being able to cycle through them -->
-  <!-- showing them on the scroll bar -->
+  <p>User agents are expected to allow users to discover the
+  destination of <a href=#hyperlink title=hyperlink>hyperlinks</a> and of
+  <a href=#the-form-element title=form>forms</a> before triggering their <a href=#navigate title=navigate>navigation</a>.</p>
 
-  <p class=XXX>The rendering section will eventually suggest
-  that user agents provide a way to let users jump between
-  <code><a href=#the-mark-element>mark</a></code> elements. Suggested rendering is a neon yellow
-  background highlight, though UAs maybe should allow this to be
-  toggled.</p>
+  <p>User agents are expected to allow users to <a href=#navigate>navigate</a>
+  <a href=#browsing-context title="browsing context">browsing contexts</a> to the
+  resources <a href=#resolve-a-url title="resolve a url">indicated</a> by the <code title="">cite</code> attributes on <code><a href=#the-q-element>q</a></code>,
+  <code><a href=#the-blockquote-element>blockquote</a></code>, <code><a href=#the-ins-element>ins</a></code>, and <code><a href=#the-del-element>del</a></code>
+  elements.</p>
 
 
 
-  <h4 id=the-contenteditable-attribute><span class=secno>10.6.4 </span>The <code title=attr-contenteditable><a href=#attr-contenteditable>contenteditable</a></code> attribute</h4>
+  <h4 id=the-mark-element-0><span class=secno>10.6.3 </span>The <code><a href=#the-mark-element>mark</a></code> element</h4>
 
-  <p class=XXX>...</p>
+  <p>User agents are expected to allow the user to cycle through all
+  the <code><a href=#the-mark-element>mark</a></code> elements in a <code>Document</code>. User
+  agents are also expected to bring their existence to the user's
+  attention, even when they are off-screen, e.g. by highlighting
+  portions of the scroll bar that represent portions of the document
+  that contain <code><a href=#the-mark-element>mark</a></code> elements.</p>
 
 
 
-  <h4 id=the-title-attribute-0><span class=secno>10.6.5 </span>The <code title=attr-title><a href=#the-title-attribute>title</a></code> attribute</h4>
+  <h4 id=the-title-attribute-0><span class=secno>10.6.4 </span>The <code title=attr-title><a href=#the-title-attribute>title</a></code> attribute</h4>
 
   <p>Given an element (e.g. the element designated by the mouse
   cursor), if the element, or one of its ancestors, has a <code title=attr-title><a href=#the-title-attribute>title</a></code> attribute, and the nearest such

diff --git a/source b/source
@@ -11027,9 +11027,9 @@ not-slash     = %x0000-002E / %x0030-%10FFFF
 
   <p>The <code>noscript</code> element has no other requirements. In
   particular, children of the <code>noscript</code> element are not
-  exempt from form submission, scripting, and so forth, even when
-  <span title="concept-n-script">scripting is enabled</span> for the
-  element.</p>
+  exempt from <span>form submission</span>, scripting, and so forth,
+  even when <span title="concept-n-script">scripting is enabled</span>
+  for the element.</p>
 
 
 
@@ -26746,7 +26746,8 @@ function AddCloud(data, x, y) { ... }</pre>
 
   <p class="note">The <code>object</code> element is also a
   <span>form-associated element</span> and can, with the use of a
-  suitable <span>plugin</span>, partake in form submission.</p>
+  suitable <span>plugin</span>, partake in <span>form
+  submission</span>.</p>
 
 
   <h4>The <dfn><code>form</code></dfn> element</h4>
@@ -32986,8 +32987,8 @@ interface <dfn>HTMLOptionElement</dfn> : <span>HTMLElement</span> {
   <h5>Naming form controls</h5>
 
   <p>The <dfn title="attr-fe-name"><code>name</code></dfn> content
-  attribute gives the name of the form control, as used in form
-  submission and in the <code>form</code> element's <code
+  attribute gives the name of the form control, as used in <span>form
+  submission</span> and in the <code>form</code> element's <code
   title="dom-form-elements">elements</code> object. If the attribute
   is specified, its value must not be the empty string.</p>
 
@@ -33552,7 +33553,7 @@ interface <dfn>HTMLOptionElement</dfn> : <span>HTMLElement</span> {
 
 
 
-  <h4>Form submission</h4>
+  <h4><dfn>Form submission</dfn></h4>
 
   <h5>Implicit submission</h5>
 
@@ -63452,31 +63453,35 @@ target element as follows:
 
 
 
-  <h4>Links</h4>
-
-  <p class="XXX">...</p>
-  <!-- hyperlinks: hover show url; clicks; opening in new browsing contexts -->
-  <!-- cite attribute on q, blockquote, ins, del: on hover, show link -->
-
-
+  <h4>Links, forms, and navigation</h4>
 
-  <h4>The <code>mark</code> element</h4>
+  <p>User agents are expected to allow the user to control aspects of
+  <span>hyperlink</span> activation and <span>form submission</span>,
+  such as which <span>browsing context</span> is to be used for the
+  subsequent <span title="navigate">navigation</span>.</p>
 
-  <p class="XXX">...</p>
-  <!-- being able to cycle through them -->
-  <!-- showing them on the scroll bar -->
+  <p>User agents are expected to allow users to discover the
+  destination of <span title="hyperlink">hyperlinks</span> and of
+  <span title="form">forms</span> before triggering their <span
+  title="navigate">navigation</span>.</p>
 
-  <p class="XXX">The rendering section will eventually suggest
-  that user agents provide a way to let users jump between
-  <code>mark</code> elements. Suggested rendering is a neon yellow
-  background highlight, though UAs maybe should allow this to be
-  toggled.</p>
+  <p>User agents are expected to allow users to <span>navigate</span>
+  <span title="browsing context">browsing contexts</span> to the
+  resources <span title="resolve a url">indicated</span> by the <code
+  title="">cite</code> attributes on <code>q</code>,
+  <code>blockquote</code>, <code>ins</code>, and <code>del</code>
+  elements.</p>
 
 
 
-  <h4>The <code title="attr-contenteditable">contenteditable</code> attribute</h4>
+  <h4>The <code>mark</code> element</h4>
 
-  <p class="XXX">...</p>
+  <p>User agents are expected to allow the user to cycle through all
+  the <code>mark</code> elements in a <code>Document</code>. User
+  agents are also expected to bring their existence to the user's
+  attention, even when they are off-screen, e.g. by highlighting
+  portions of the scroll bar that represent portions of the document
+  that contain <code>mark</code> elements.</p>