[html5] r3541 - obsolete file

whatwg at whatwg.org whatwg at whatwg.org
Wed Aug 5 15:19:07 PDT 2009


Author: ianh
Date: 2009-08-05 15:19:06 -0700 (Wed, 05 Aug 2009)
New Revision: 3541

Removed:
   header-whatwg
Modified:
   index
Log:
obsolete file

Deleted: header-whatwg
===================================================================
--- header-whatwg	2009-08-05 01:34:10 UTC (rev 3540)
+++ header-whatwg	2009-08-05 22:19:06 UTC (rev 3541)
@@ -1,213 +0,0 @@
-<!DOCTYPE html>
-<html lang="en-US-x-hixie">
- <head>
-  <title>HTML 5</title>
-  <link rel="stylesheet" href="/style/specification">
-  <link rel="icon" href="/images/icon">
-  <style>
-   .proposal { border: blue solid; padding: 1em; }
-   .bad, .bad *:not(.XXX) { color: gray; border-color: gray; background: transparent; }
-   table.matrix, table.matrix td { border: none; text-align: right; }
-   table.matrix { margin-left: 2em; }
-   .dice-example { border-collapse: collapse; border-style: hidden solid solid hidden; border-width: thin; margin-left: 3em; }
-   .dice-example caption { width: 30em; font-size: smaller; font-style: italic; padding: 0.75em 0; text-align: left; }
-   .dice-example td, .dice-example th { border: solid thin; width: 1.35em; height: 1.05em; text-align: center; padding: 0; }
-   .applies th > * { display: block; white-space: nowrap; }
-   #updatesStatus { display: none; }
-   #updatesStatus.relevant { display: block; position: fixed; right: 1em; top: 1em; padding: 0.5em; font: bold small sans-serif; min-width: 25em; width: 30%; max-width: 40em; height: auto; border: ridge 4px gray; background: #EEEEEE; color: black; }
-   #configUI { position: absolute; top: 10em; right: 1em; width: 11em; font-size: small; text-align: center; }
-   #configUI p { padding: 0.3em; background: #EEEEEE; color: black; border: inset thin; }
-   #configUI input[type=button] { display: block; margin: auto; }
-   @media print { #configUI { display: none; } }
-   .rfc2119 { font-variant: small-caps; text-shadow: 0 0 0.5em yellow; position: static; }
-   .rfc2119::after { position: absolute; left: 0; width: 25px; text-align: center; color: yellow; text-shadow: 0.075em 0.075em 0.2em black; }
-   .rfc2119.m\ust::after { content: '\2605'; }
-   .rfc2119.s\hould::after { content: '\2606'; }
-   [hidden] { display: none; }
-  </style>
-  <link rel="stylesheet" title="Complete specification" href="data:text/css,">
-  <link rel="alternate stylesheet" title="Author documentation only"
-        href="data:text/css,.impl%20{%20display:%20none;%20}">
-  <link rel="alternate stylesheet" title="Highlight implementation requirements"
-        href="data:text/css,.impl%20{%20background:%20#FFEEEE;%20}">
-  <link rel="stylesheet" href="status.css">
-  <script>
-   var loadTimer = new Date();
-   function load(script) {
-     var e = document.createElement('script');
-     e.setAttribute('src', script);
-     document.body.appendChild(e);
-   }
-   function init() {
-     if (location.search == '?slow-browser')
-       return;
-     load('status.js');
-     load('dfn.js');
-     load('toc.js');
-     if (location.search == '?profile')
-       document.getElementsByTagName('h2')[0].textContent += '; load: ' + (new Date() - loadTimer) + 'ms';
-   }
-  </script>
- </head>
- <body class="draft" onload="init()">
-
-  <div class="head">
-   <p><a rel="home" href="http://www.whatwg.org/" class="logo"><img alt="WHATWG" src="/images/logo"></a></p>
-   <h1>HTML 5</h1>
-   <h2 class="no-num no-toc">Draft Recommendation — [DATE: 01 Jan 1901]</h2>
-   <p>You can take part in this work. <a href="http://www.whatwg.org/mailing-list">Join the working group's discussion list.</a></p>
-   <p><strong>Web designers!</strong> We have a <a href="http://blog.whatwg.org/faq/">FAQ</a>, a <a href="http://forums.whatwg.org/">forum</a>, and a <a href="http://www.whatwg.org/mailing-list#help">help mailing list</a> for you!</p>
-   <dl>
-    <dt>Multiple-page version:</dt>
-    <dd><strong><a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/">http://whatwg.org/html5</a></strong></dd>
-    <dt>One-page version:</dt>
-    <dd><a href="http://www.whatwg.org/specs/web-apps/current-work/">http://www.whatwg.org/specs/web-apps/current-work/</a></dd>
-    <dt>PDF print versions:</dt>
-    <dd>A4: <a href="http://www.whatwg.org/specs/web-apps/current-work/html5-a4.pdf">http://www.whatwg.org/specs/web-apps/current-work/html5-a4.pdf</a></dd>
-    <dd>Letter: <a href="http://www.whatwg.org/specs/web-apps/current-work/html5-letter.pdf">http://www.whatwg.org/specs/web-apps/current-work/html5-letter.pdf</a></dd>
-    <dt>Version history:</dt>
-    <dd>Twitter messages (non-editorial changes only): <a href="http://twitter.com/WHATWG">http://twitter.com/WHATWG</a></dd>
-    <dd>Commit-Watchers mailing list: <a href="http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org">http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org</a></dd>
-    <dd>Interactive Web interface: <a href="http://html5.org/tools/web-apps-tracker">http://html5.org/tools/web-apps-tracker</a></dd>
-    <dd>Subversion interface: <a href="http://svn.whatwg.org/">http://svn.whatwg.org/</a></dd>
-    <dd>HTML diff with the last version in Subversion: <a href="index-diff">http://whatwg.org/specs/web-apps/current-work/index-diff</a></dd>
-    <dt>Issues:</dt>
-    <dd>To send feedback: <a href="http://www.whatwg.org/mailing-list">whatwg at whatwg.org</a></dd>
-    <dd>To view and vote on feedback: <a href="http://www.whatwg.org/issues/">http://www.whatwg.org/issues/</a></dd>
-    <dt>Editor:</dt>
-    <dd>Ian Hickson, Google, ian at hixie.ch</dd>
-   </dl>
-   <p class="copyright">© Copyright 2004-2009 Apple Computer, Inc.,
-   Mozilla Foundation, and Opera Software ASA.</p>
-   <p class="copyright">You are granted a license to use, reproduce
-   and create derivative works of this document.</p>
-  </div>
-
-  <hr>
-
-  <h2 class="no-num no-toc" id="abstract">Abstract</h2>
-
-  <p>This specification evolves HTML and its related APIs to ease the
-  authoring of Web-based applications. Additions include context
-  menus, a direct-mode graphics canvas, a full duplex client-server
-  communication channel, more semantics, audio and video, various
-  features for offline Web applications, sandboxed iframes, and scoped
-  styling. Heavy emphasis is placed on keeping the language backwards
-  compatible with existing legacy user agents and on keeping user
-  agents backwards compatible with existing legacy documents.</p>
-
-
-  <h2 class="no-num no-toc" id="status">Status of this document</h2>
-
-  <p><strong>This is a work in progress!</strong> This document is
-  changing on a daily if not hourly basis in response to comments and
-  as a general part of its development process. Comments are very
-  welcome, please send them to <a
-  href="mailto:whatwg at whatwg.org">whatwg at whatwg.org</a>. Thank
-  you.</p>
-
-  <p>The current focus is in responding to the <a
-  href="http://www.whatwg.org/issues/">outstanding
-  feedback</a>. (There is <a
-  href="http://www.whatwg.org/issues/data.html">a chart</a> showing
-  current progress.)</p>
-
-  <p>Implementors should be aware that this specification is not
-  stable. <strong>Implementors who are not taking part in the
-  discussions are likely to find the specification changing out from
-  under them in incompatible ways.</strong> Vendors interested in
-  implementing this specification before it eventually reaches the
-  call for implementations should join the <a
-  href="/mailing-list">WHATWG mailing list</a> and take part in the
-  discussions.</p>
-
-  <p>This specification is also being produced by the <a
-  href="http://www.w3.org/html/wg">W3C HTML WG</a>. The two
-  specifications are identical from the table of contents onwards.</p>
-
-  <p>This specification is intended to replace (be the new version of)
-  what was previously the HTML4, XHTML 1.x, and DOM2 HTML
-  specifications.</p>
-
-
-  <script>
-   function getCookie(name) {
-     var cookies = document.cookie.split("; ");
-     for (var index = 0; index < cookies.length; index++) {
-       var data = cookies[index].split("=");
-       if (data[0] == name)
-         return unescape(data[1]);
-     }
-     return null;
-   }
-   var current_revision = "r" + "$Revision: 0 $".substr(11);
-   current_revision = current_revision.substr(0, current_revision.length - 2);
-   var last_known_revision = current_revision;
-   function getRemoteString(url, callback) {
-     var x = new XMLHttpRequest();
-     x.open('GET', url + "?" + new Date());
-     x.onreadystatechange = function () {
-       if (x.readyState == 4) {
-         if (x.status == 200)
-           callback(x.responseText);
-         else
-           throw 'network error ' + x.status + ': "' + x.statusText + '" while loading ' + url;
-       }
-     };
-     x.send(null);
-   }
-   function doUpdate() {
-     getRemoteString('revision.dat', function (data) {
-       if (data != last_known_revision) {
-         getRemoteString('revision-message.dat', function (message) {
-           last_known_revision = data;
-           var status = document.getElementById('updatesStatus');
-           status.textContent = 'This specification has been updated. You are reading ' + current_revision + ' but the latest revision is ' + data + ' ("' +
-                                message + '") ';
-           var a = document.createElement('a');
-           a.href = '';
-           a.onclick = function () { location.reload(); return false; };
-           a.textContent = "Reload";
-           status.appendChild(a);
-           status.appendChild(document.createTextNode('. '));
-           var d = document.createElement('a');
-           d.href = 'http://html5.org/tools/web-apps-tracker?from=' + current_revision.substr(1) + '&to=' + data.substr(1);
-           d.textContent = "Diffs";
-           status.appendChild(d);
-           status.appendChild(document.createTextNode('. '));
-           var x = document.createElement('a');
-           x.href = '';
-           x.onclick = function () { status.textContent = ''; status.className = ''; return false; };
-           x.textContent = "Close";
-           status.appendChild(x);
-           status.appendChild(document.createTextNode('. '));
-           status.className = 'relevant';
-         });
-       }
-     });
-   }
-   var updater;
-   function configureUpdates(on) {
-     var date = new Date();
-     date.setFullYear(date.getFullYear() + 1);
-     document.cookie = 'updatesEnabled=' + encodeURIComponent(on?'1':'0') + '; expires=' + date.toGMTString();
-     if (updater && !on)
-       clearInterval(updater);
-     if (!updater && on)
-       updater = setInterval(doUpdate, 30000);
-     if (on)
-       doUpdate();
-   }
-  </script>
-
-  <div id="configUI"><p id="updatesUI"><label><input type=checkbox
-  id="updatesEnabled" onchange="configureUpdates(this.checked)"> Watch
-  for updates</label></p></div>
-  <p id="updatesStatus"></p>
-
-  <script>
-   if (getCookie('updatesEnabled') == '1') {
-     document.getElementById('updatesEnabled').checked = true;
-     configureUpdates(true);
-   }
-  </script>

Modified: index
===================================================================
--- index	2009-08-05 01:34:10 UTC (rev 3540)
+++ index	2009-08-05 22:19:06 UTC (rev 3541)
@@ -26723,6 +26723,49 @@
   </dl><p>Authors may also use other techniques, or combinations of the
   above techniques, as appropriate.</p>
 
+  <p>The <dfn id=attr-table-summary title=attr-table-summary><code>summary</code></dfn>
+  attribute on <code><a href=#the-table-element>table</a></code> elements was suggested in earlier
+  versions of the language as a technique for providing explanatory
+  text for complex tables for users of screen readers. One of the <a href=#table-descriptions>techniques</a> described <!--in the
+  <code>table</code> section--> above should be used
+  instead. <!--Authors should not specify the <code
+  title="attr-table-summary">summary</code> attribute on
+  <code>table</code> elements. --> <!-- 2.65% pages --></p>
+
+  <p class=note>In particular, authors are encouraged to consider
+  whether their explanatory text for tables is likely to be useful to
+  the visually impaired: if their text would not be useful, then it is
+  best to not include a <code title=attr-table-summary><a href=#attr-table-summary>summary</a></code> attribute. Similarly, if
+  their explanatory text could help someone who is not visually
+  impaired, e.g. someone who is seeing the table for the first time,
+  then the text would be more useful before the table or in the
+  <code><a href=#the-caption-element>caption</a></code>. For example, describing the conclusions of the
+  data in a table is useful to everyone; explaining how to read the
+  table, if not obvious from the headers alone, is useful to everyone;
+  describing the structure of the table, if it is easy to grasp
+  visually, may not be useful to everyone, but it might also not be
+  useful to users who can quickly navigate the table with an
+  accessibility tool.</p>
+
+  <!--
+  <p class="note">Use of the <code
+  title="attr-table-summary">summary</code> attribute is discouraged
+  because in practice it is poorly understood. Because the attribute
+  is not exposed in visual user agents, authors who have included it
+  have typically not been able to test it, and have therefore set the
+  attribute to values that are of no use to users of accessibility
+  tools. This has lead to accessibility tools introducing heuristics
+  to try to avoid exposing such usage of the attribute to users. Even
+  the few authors who have made the best use of the attribute have
+  often misused it, for example by including text that would in fact
+  be useful for all users, or that is redundant with other information
+  on the page separate from the table.</p>
+
+  <p class="XXX">It has been suggested that the summary="" attribute
+  should not be obsolete, and the working group may vote on the matter
+  at some future point.</p>
+  -->
+
   <div class=impl>
 
   <p>If a <code><a href=#the-table-element>table</a></code> element has a <code title=attr-table-summary><a href=#attr-table-summary>summary</a></code> attribute, the user agent
@@ -70783,31 +70826,11 @@
   attribute. The <code title=attr-id><a href=#the-id-attribute>id</a></code> attribute should be
   used instead.</p>
 
-  <p>Authors should not specify the <dfn id=attr-table-summary title=attr-table-summary><code>summary</code></dfn> attribute on
-  <code><a href=#the-table-element>table</a></code> elements. <!-- 2.65% pages --> This attribute was
-  suggested in earlier versions of the language as a technique for
-  providing explanatory text for complex tables for users of screen
-  readers. One of the <a href=#table-descriptions>techniques</a>
-  described in the <code><a href=#the-table-element>table</a></code> section should be used
-  instead.</p>
+  <p class=note>The <code title=attr-table-summary><a href=#attr-table-summary>summary</a></code>
+  attribute, defined in the <code><a href=#the-table-element>table</a></code> section, will also
+  trigger a warning.</p>
 
-  <p class=note>Use of the <code title=attr-table-summary><a href=#attr-table-summary>summary</a></code> attribute is discouraged
-  because in practice it is poorly understood. Because the attribute
-  is not exposed in visual user agents, authors who have included it
-  have typically not been able to test it, and have therefore set the
-  attribute to values that are of no use to users of accessibility
-  tools. This has lead to accessibility tools introducing heuristics
-  to try to avoid exposing such usage of the attribute to users. Even
-  the few authors who have made the best use of the attribute have
-  often misused it, for example by including text that would in fact
-  be useful for all users, or that is redundant with other information
-  on the page separate from the table.</p>
 
-  <p class=XXX>It has been suggested that the summary="" attribute
-  should not be obsolete, and the working group may vote on the matter
-  at some future point.</p>
-
-
   <div class=impl>
 
   <h4 id=warnings-for-obsolete-but-conforming-features><span class=secno>12.1.1 </span>Warnings for obsolete but conforming features</h4>




More information about the Commit-Watchers mailing list