hixie: Apply W3C chair revert request (to W3C copy only). Fix markup typo. (whatwg r6980) from poot on 2012-02-08 (public-html-diffs@w3.org from February 2012)

From: poot <cvsmail@w3.org>
Date: Wed, 08 Feb 2012 18:00:16 -0500
To: public-html-diffs@w3.org
Message-Id: <E1RvGUq-0005ie-7e@jay.w3.org>
hixie: Apply W3C chair revert request (to W3C copy only). Fix markup
typo. (whatwg r6980)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5574&r2=1.5575&f=h
http://html5.org/tools/web-apps-tracker?from=6979&to=6980

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5574
retrieving revision 1.5575
diff -u -d -r1.5574 -r1.5575
--- Overview.html 8 Feb 2012 00:31:26 -0000 1.5574
+++ Overview.html 8 Feb 2012 22:59:57 -0000 1.5575
@@ -9468,11 +9468,11 @@
   element's <code title="attr-translate"><a href="#attr-translate">translate</a></code> attribute is
   in the <i>no</i> state, then the element's <a href="#translation-mode">translation
   mode</a> is in the <a href="#no-translate">no-translate</a> state. Otherwise,
-  the element's code title="attr-translate"&gt;translate attribute
-  is in the <i>inherit</i> state; in that case, the element's
-  <a href="#translation-mode">translation mode</a> is in the same state as its parent
-  element, if any, or in the <a href="#translate-enabled">translate-enabled</a> state, if
-  the element is a <a href="#root-element">root element</a>.<p>When an element is in the <dfn id="translate-enabled">translate-enabled</dfn> state, the
+  the element's <code title="attr-translate"><a href="#attr-translate">translate</a></code>
+  attribute is in the <i>inherit</i> state; in that case, the
+  element's <a href="#translation-mode">translation mode</a> is in the same state as its
+  parent element, if any, or in the <a href="#translate-enabled">translate-enabled</a>
+  state, if the element is a <a href="#root-element">root element</a>.<p>When an element is in the <dfn id="translate-enabled">translate-enabled</dfn> state, the
   element's attribute values and the values of its <code><a href="#text">Text</a></code>
   node children are to be translated when the page is localized.<p>When an element is in the <dfn id="no-translate">no-translate</dfn> state, the
   element's attribute values and the values of its <code><a href="#text">Text</a></code>
@@ -54512,12 +54512,17 @@
     <li><p>Return 1.</li>
 
    </ol></div><h2 id="editing"><span class="secno">7 </span><dfn>User interaction</dfn></h2><h3 id="the-hidden-attribute"><span class="secno">7.1 </span>The <dfn title="attr-hidden"><code>hidden</code></dfn> attribute</h3><p>All <a href="#html-elements">HTML elements</a> may have the <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> content attribute set. The <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute is a <a href="#boolean-attribute">boolean
-  attribute</a>. When specified on an element, it indicates that
-  the element is not yet, or is no longer, directly relevant to the
-  page's current state, or that it is being used to declare content to
-  be reused by other parts of the page as opposed to being directly
-  accessed by the user. <span class="impl">User agents should not
-  render elements that have the <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute specified.</span><div class="example">
+  attribute</a>.
+
+
+  When specified on an element, it indicates that the element is not
+  yet, or is no longer, relevant.
+
+
+
+  <span class="impl">User agents should not render elements that have
+  the <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute
+  specified.</span><div class="example">
 
    <p>In the following skeletal example, the attribute is used to hide
    the Web game's main screen until the user logs in:</p>
@@ -54549,28 +54554,22 @@
   controls in one big page with a scrollbar. It is similarly incorrect
   to use this attribute to hide content just from one presentation
   &mdash; if something is marked <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code>, it is hidden from all
-  presentations, including, for instance, screen readers.</p><p>Elements that are not themselves <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> must not <a href="#hyperlink">hyperlink</a> to
-  elements that are <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code>. The <code title="">for</code> attributes of <code><a href="#the-label-element">label</a></code> and
-  <code><a href="#the-output-element">output</a></code> elements that are not themselves <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> must similarly not refer to
-  elements that are <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code>. In both
-  cases, such references would cause user confusion.<p>Elements and scripts may, however, refer to elements that are
-  <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> in other contexts.<div class="example">
+  presentations, including, for instance, screen readers.</p><p>Elements that are not <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code>
+  should not link to or refer to elements that are <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code>.<div class="example">
 
    <p>For example, it would be incorrect to use the <code title="attr-hyperlink-href"><a href="#attr-hyperlink-href">href</a></code> attribute to link to a
    section marked with the <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code>
    attribute. If the content is not applicable or relevant, then there
    is no reason to link to it.</p>
 
-   <p>It would be fine, however, to use the ARIA <code title="attr-aria-describedby">aria-describedby</code> attribute to
-   refer to descriptions that are themselves <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code>. While hiding the descriptions
-   implies that they are not useful alone, they could be written in
-   such a way that they are useful in the specific context of being
-   referenced from the images that they describe.</p>
 
-   <p>Similarly, a <code><a href="#the-canvas-element">canvas</a></code> element with the <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute could be used by a
-   scripted graphics engine as an off-screen buffer, and a form
-   control could refer to a hidden <code><a href="#the-form-element">form</a></code> element using its
-   <code title="attr-fae-form"><a href="#attr-fae-form">form</a></code> attribute.</p>
+   <p>It would similarly be incorrect to use the ARIA <code title="attr-aria-describedby">aria-describedby</code> attribute to
+   refer to descriptions that are themselves <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code>. Hiding a section means that it
+   is not applicable or relevant to anyone at the current time, so
+   clearly it cannot be a valid description of content the user can
+   interact with.</p>
+
+
 
   </div><p>Elements in a section hidden by the <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute are still active,
   e.g. scripts and form controls in such sections still execute
Received on Wednesday, 8 February 2012 23:00:24 UTC