[html5] r7188 - [e] (0) Source cleanup: remove the text that the HTMLWG version has that is all [...]

whatwg at whatwg.org whatwg at whatwg.org
Thu Jul 19 20:40:58 PDT 2012


Author: ianh
Date: 2012-07-19 20:40:57 -0700 (Thu, 19 Jul 2012)
New Revision: 7188

Modified:
   complete.html
   index
   source
Log:
[e] (0) Source cleanup: remove the text that the HTMLWG version has that is all wishy washy about presentational tables for no good reason.
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2012-07-20 03:37:47 UTC (rev 7187)
+++ complete.html	2012-07-20 03:40:57 UTC (rev 7188)
@@ -41987,8 +41987,6 @@
   may report the contents of that attribute to the user.</p>
   </div>
 
-<!--FORK-->
-
   <p>Tables must not be used as layout aids.
 
   Historically, some Web authors have misused tables in HTML as a way
@@ -42000,46 +41998,6 @@
   likely to find it very difficult to navigate pages with tables used
   for layout.</p>
 
-  <!-- The paragraph below replaces the above one in the W3C copy due
-  to a WG decision. It is not used in the WHATWG copy for the
-  following reasons:
-
-   * "should not" implies that there may be valid reasons to use
-     tables for layout, which there are not.
-
-   * The second sentence appears to be grammatically incorrect, and
-     more importantly, does not clearly state that use of tables for
-     layout has always been a misuse. This implies it may have once
-     been correct (even though that is not the case), and that further
-     may reduce the effectiveness of advocacy on this topic.
-
-   * The third sentence (in the paragraph below) is identical to the
-     fourth one in the paragraph above except for comma usage which
-     seems incorrect (it implies that the users are the screen
-     readers, as opposed to the tools, if I'm reading it right).
-
-   * The final sentence below flat out legitimizes layout tables.
-
-   * The paragraph below seems to assume that only ARIA-enabled ATs
-     are a concern, when in fact there are numerous UAs other than
-     ARIA-enabled ATs that are harmed by this use of layout tables.
-
-   * The paragraph below fails to suggest that UAs will need
-     heuristics to deal with the existing content.
-
-   * The text below actually contradicts other requirements in this
-     specification (<table>s represent tables, and elements must be
-     used per their semantics, so the requirement that tables not be
-     used for layout is in fact technically redundant, and the
-     paragraph below doesn't change that).
-
-   * There really is no good reason to use tables for layout anymore,
-     and conformance criteria should support best practices, not
-     obsolete authoring practices.
-
-  -->
-
-
   <p class=note>There are a variety of alternatives to using HTML
   tables for layout, primarily using CSS positioning and the CSS table
   model.</p>
@@ -42055,14 +42013,12 @@
 
 
   <div class=impl>
+
   <hr><p>Tables can be complicated to understand and navigate. To help
   users with this, user agents should clearly delineate cells in a
   table from each other, unless the user agent has classified the
-  table as a
-<!--FORK-->
-  (non-conforming)
-<!--FORK-->
-  layout table.</p>
+  table as a (non-conforming) layout table.</p>
+
   </div>
 
   <p class=note>Authors <span class=impl>and implementors</span>
@@ -42694,7 +42650,6 @@
 the cell that corresponds to the values of the two dice.
 </caption></pre>
 
-<!--HTML4POLICE (hidden in w3c version because w3c version has to be valid HTML4) --><!--FORK-->
    <p>This provides the user with more context:</p>
 
    <table class=dice-example><caption>
@@ -42711,7 +42666,7 @@
     <tr><th> 4 <td> 5 <td> 6 <td> 7 <td> 8 <td> 9 <td> 10
     <tr><th> 5 <td> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11
     <tr><th> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11 <td> 12
-   </table><!--HTML4POLICE--><!--FORK--></div>
+   </table></div>
 
 
 
@@ -44514,7 +44469,6 @@
    <td>29.0%
 </table></pre>
 
-<!--HTML4POLICE--><!--FORK-->
   <p>This table could look like this:</p>
 
   <table class="apple-table-examples e1"><thead><tr><th>
@@ -44537,7 +44491,7 @@
      <td>34.3%
      <td>34.0%
      <td>29.0%
-  </table><!--HTML4POLICE--><!--FORK--><hr><p>The following shows how one might mark up the operating expenses
+  </table><hr><p>The following shows how one might mark up the operating expenses
   table from lower on the same page of that document:</p>
 
   <pre><table>

Modified: index
===================================================================
--- index	2012-07-20 03:37:47 UTC (rev 7187)
+++ index	2012-07-20 03:40:57 UTC (rev 7188)
@@ -41987,8 +41987,6 @@
   may report the contents of that attribute to the user.</p>
   </div>
 
-<!--FORK-->
-
   <p>Tables must not be used as layout aids.
 
   Historically, some Web authors have misused tables in HTML as a way
@@ -42000,46 +41998,6 @@
   likely to find it very difficult to navigate pages with tables used
   for layout.</p>
 
-  <!-- The paragraph below replaces the above one in the W3C copy due
-  to a WG decision. It is not used in the WHATWG copy for the
-  following reasons:
-
-   * "should not" implies that there may be valid reasons to use
-     tables for layout, which there are not.
-
-   * The second sentence appears to be grammatically incorrect, and
-     more importantly, does not clearly state that use of tables for
-     layout has always been a misuse. This implies it may have once
-     been correct (even though that is not the case), and that further
-     may reduce the effectiveness of advocacy on this topic.
-
-   * The third sentence (in the paragraph below) is identical to the
-     fourth one in the paragraph above except for comma usage which
-     seems incorrect (it implies that the users are the screen
-     readers, as opposed to the tools, if I'm reading it right).
-
-   * The final sentence below flat out legitimizes layout tables.
-
-   * The paragraph below seems to assume that only ARIA-enabled ATs
-     are a concern, when in fact there are numerous UAs other than
-     ARIA-enabled ATs that are harmed by this use of layout tables.
-
-   * The paragraph below fails to suggest that UAs will need
-     heuristics to deal with the existing content.
-
-   * The text below actually contradicts other requirements in this
-     specification (<table>s represent tables, and elements must be
-     used per their semantics, so the requirement that tables not be
-     used for layout is in fact technically redundant, and the
-     paragraph below doesn't change that).
-
-   * There really is no good reason to use tables for layout anymore,
-     and conformance criteria should support best practices, not
-     obsolete authoring practices.
-
-  -->
-
-
   <p class=note>There are a variety of alternatives to using HTML
   tables for layout, primarily using CSS positioning and the CSS table
   model.</p>
@@ -42055,14 +42013,12 @@
 
 
   <div class=impl>
+
   <hr><p>Tables can be complicated to understand and navigate. To help
   users with this, user agents should clearly delineate cells in a
   table from each other, unless the user agent has classified the
-  table as a
-<!--FORK-->
-  (non-conforming)
-<!--FORK-->
-  layout table.</p>
+  table as a (non-conforming) layout table.</p>
+
   </div>
 
   <p class=note>Authors <span class=impl>and implementors</span>
@@ -42694,7 +42650,6 @@
 the cell that corresponds to the values of the two dice.
 </caption></pre>
 
-<!--HTML4POLICE (hidden in w3c version because w3c version has to be valid HTML4) --><!--FORK-->
    <p>This provides the user with more context:</p>
 
    <table class=dice-example><caption>
@@ -42711,7 +42666,7 @@
     <tr><th> 4 <td> 5 <td> 6 <td> 7 <td> 8 <td> 9 <td> 10
     <tr><th> 5 <td> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11
     <tr><th> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11 <td> 12
-   </table><!--HTML4POLICE--><!--FORK--></div>
+   </table></div>
 
 
 
@@ -44514,7 +44469,6 @@
    <td>29.0%
 </table></pre>
 
-<!--HTML4POLICE--><!--FORK-->
   <p>This table could look like this:</p>
 
   <table class="apple-table-examples e1"><thead><tr><th>
@@ -44537,7 +44491,7 @@
      <td>34.3%
      <td>34.0%
      <td>29.0%
-  </table><!--HTML4POLICE--><!--FORK--><hr><p>The following shows how one might mark up the operating expenses
+  </table><hr><p>The following shows how one might mark up the operating expenses
   table from lower on the same page of that document:</p>
 
   <pre><table>

Modified: source
===================================================================
--- source	2012-07-20 03:37:47 UTC (rev 7187)
+++ source	2012-07-20 03:40:57 UTC (rev 7188)
@@ -49054,8 +49054,6 @@
   may report the contents of that attribute to the user.</p>
   </div>
 
-<!--END w3c-html--><!--FORK-->
-
   <p>Tables must not be used as layout aids.
 
   Historically, some Web authors have misused tables in HTML as a way
@@ -49067,65 +49065,6 @@
   likely to find it very difficult to navigate pages with tables used
   for layout.</p>
 
-  <!-- The paragraph below replaces the above one in the W3C copy due
-  to a WG decision. It is not used in the WHATWG copy for the
-  following reasons:
-
-   * "should not" implies that there may be valid reasons to use
-     tables for layout, which there are not.
-
-   * The second sentence appears to be grammatically incorrect, and
-     more importantly, does not clearly state that use of tables for
-     layout has always been a misuse. This implies it may have once
-     been correct (even though that is not the case), and that further
-     may reduce the effectiveness of advocacy on this topic.
-
-   * The third sentence (in the paragraph below) is identical to the
-     fourth one in the paragraph above except for comma usage which
-     seems incorrect (it implies that the users are the screen
-     readers, as opposed to the tools, if I'm reading it right).
-
-   * The final sentence below flat out legitimizes layout tables.
-
-   * The paragraph below seems to assume that only ARIA-enabled ATs
-     are a concern, when in fact there are numerous UAs other than
-     ARIA-enabled ATs that are harmed by this use of layout tables.
-
-   * The paragraph below fails to suggest that UAs will need
-     heuristics to deal with the existing content.
-
-   * The text below actually contradicts other requirements in this
-     specification (<table>s represent tables, and elements must be
-     used per their semantics, so the requirement that tables not be
-     used for layout is in fact technically redundant, and the
-     paragraph below doesn't change that).
-
-   * There really is no good reason to use tables for layout anymore,
-     and conformance criteria should support best practices, not
-     obsolete authoring practices.
-
-  -->
-
-<!--END complete--><!--END dev-html--><!--START w3c-html--><!--FORK-->
-
-  <p>Tables should not be used as layout aids.
-
-  Historically, many Web authors have tables in HTML as a way to
-  control their page layout making it difficult to extract tabular
-  data from such documents.
-
-  In particular, users of accessibility tools, like screen readers,
-  are likely to find it very difficult to navigate pages with tables
-  used for layout.
-
-  If a table is to be used for layout it must be marked with the
-  attribute role="presentation" for a user agent to properly represent
-  the table to an assistive technology and to properly convey the
-  intent of the author to tools that wish to extract tabular data from
-  the document.</p>
-
-<!--START complete--><!--START dev-html--><!--FORK-->
-
   <p class="note">There are a variety of alternatives to using HTML
   tables for layout, primarily using CSS positioning and the CSS table
   model.</p>
@@ -49141,15 +49080,14 @@
 
 
   <div class="impl">
+
   <hr>
+
   <p>Tables can be complicated to understand and navigate. To help
   users with this, user agents should clearly delineate cells in a
   table from each other, unless the user agent has classified the
-  table as a
-<!--END w3c-html--><!--FORK-->
-  (non-conforming)
-<!--START w3c-html--><!--FORK-->
-  layout table.</p>
+  table as a (non-conforming) layout table.</p>
+
   </div>
 
   <p class="note">Authors <span class="impl">and implementors</span>
@@ -49847,7 +49785,6 @@
 the cell that corresponds to the values of the two dice.
 </caption></pre>
 
-<!--END w3c-html--><!--HTML4POLICE (hidden in w3c version because w3c version has to be valid HTML4) --><!--FORK-->
    <p>This provides the user with more context:</p>
 
    <table class="dice-example">
@@ -49866,7 +49803,6 @@
     <tr> <th> 5 <td> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11
     <tr> <th> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11 <td> 12
    </table>
-<!--START w3c-html--><!--HTML4POLICE--><!--FORK-->
 
   </div>
 
@@ -52069,7 +52005,6 @@
    <td>29.0%
 </table></pre>
 
-<!--END w3c-html--><!--HTML4POLICE--><!--FORK-->
   <p>This table could look like this:</p>
 
   <table class="apple-table-examples e1">
@@ -52103,7 +52038,6 @@
      <td>34.0%
      <td>29.0%
   </table>
-<!--START w3c-html--><!--HTML4POLICE--><!--FORK-->
 
   <hr>
 




More information about the Commit-Watchers mailing list