HTML Standard Tracker


File a bug

SVNBugCommentTime (UTC)
2770Filling in the rendering section: <mark>, links.2009-02-10 00:51
@@ -11020,23 +11020,23 @@ not-slash     = %x0000-002E / %x0030-%10FFFF
   <p>The <code>noscript</code> element must not be used in <span>XML
   <p class="note"><strong>The <code>noscript</code> element is only
   effective in the <span>HTML serialization</span><!-- XXX xref -->,
   it has no effect in the <span>XML serialization</span><!-- XXX xref
   <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>
   <h4>The <dfn><code>eventsource</code></dfn> element</h4>
   <dl class="element">
    <dd><span>Metadata content</span>.</dd>
    <dd><span>Flow content</span>.</dd>
    <dd><span>Phrasing content</span>.</dd>
@@ -26739,21 +26739,22 @@ function AddCloud(data, x, y) { ... }</pre>
   <p>In addition, some <span title="category-submit">submittable
   elements</span> can be, depending on their attributes, <dfn
   title="concept-button">buttons</dfn>. The prose below defines when
   an element is a button. Some buttons are specifically <dfn
   title="concept-submit-button">submit buttons</dfn>.</p>
   <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>
   <dl class="element">
    <dd><span>Flow content</span>.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>Where <span>flow content</span> is expected.</dd>
    <dt>Content model:</dt>
@@ -32979,22 +32980,22 @@ interface <dfn>HTMLOptionElement</dfn> : <span>HTMLElement</span> {
   <span>form owner</span>, it is <span>barred from constraint
   <h4><dfn>Attributes common to form controls</dfn></h4>
   <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>
   <p><strong>Constraint validation:</strong> If an element does not
   have a <code title="attr-fe-name">name</code> attribute specified,
   or its <code title="attr-fe-name">name</code> attribute's value is
   the empty string, then it is <span>barred from constraint
   <p>The <dfn title="dom-fe-name"><code>name</code></dfn> DOM
@@ -33545,21 +33546,21 @@ interface <dfn>HTMLOptionElement</dfn> : <span>HTMLElement</span> {
   validation can be intentionally bypassed by hostile users, and
   unintentionally bypassed by users of older user agents or automated
   tools that do not implement these features. The constraint
   validation features are only intended to improve the user
   experience, not to provide any kind of security mechanism.</p>
-  <h4>Form submission</h4>
+  <h4><dfn>Form submission</dfn></h4>
   <h5>Implicit submission</h5>
   <p>User agents may establish a <span
   title="concept-button">button</span> in each form as being the
   form's <dfn>default button</dfn>. This should be the first <span
   title="concept-submit-button">submit button</span> in <span>tree
   order</span> whose <span>form owner</span> is that <code>form</code>
   element, but user agents may pick another button if another would be
   more appropriate for the platform. If the platform supports letting
@@ -63445,45 +63446,49 @@ target element as follows:
       assigned to X in step D was some other element, assign the
       element originally assigned in step D back to X.
    I. The event goes to X. STOP
-  <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>
   <h4>The <code title="attr-title">title</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">title</code> attribute, and the nearest such
   attribute has a value that is not the empty string, it is expected
   that the user agent will expose the contents of that attribute as a