[html5] r1535 - /

whatwg at whatwg.org whatwg at whatwg.org
Tue May 6 18:00:26 PDT 2008


Author: ianh
Date: 2008-05-06 18:00:25 -0700 (Tue, 06 May 2008)
New Revision: 1535

Modified:
   header-whatwg
   index
   source
Log:
[e] (0) Update the abstract a little; minor markup fix.

Modified: header-whatwg
===================================================================
--- header-whatwg	2008-05-07 00:55:05 UTC (rev 1534)
+++ header-whatwg	2008-05-07 01:00:25 UTC (rev 1535)
@@ -54,11 +54,14 @@
 
   <h2 class="no-num no-toc" id="abstract">Abstract</h2>
 
-  <p>This specification introduces features to HTML and the DOM that
-  ease the authoring of Web-based applications. Additions include the
-  context menus, a direct-mode graphics canvas, inline popup windows,
-  and server-sent events.</p>
+  <p>This specification evolves HTML and its related APIs to ease the
+  authoring of Web-based applications. Additions include the context
+  menus, a direct-mode graphics canvas, inline popup windows, and
+  server-sent events. 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

Modified: index
===================================================================
--- index	2008-05-07 00:55:05 UTC (rev 1534)
+++ index	2008-05-07 01:00:25 UTC (rev 1535)
@@ -97,10 +97,12 @@
 
   <h2 class="no-num no-toc" id=abstract>Abstract</h2>
 
-  <p>This specification introduces features to HTML and the DOM that ease the
+  <p>This specification evolves HTML and its related APIs to ease the
    authoring of Web-based applications. Additions include the context menus,
    a direct-mode graphics canvas, inline popup windows, and server-sent
-   events.
+   events. 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.
 
   <h2 class="no-num no-toc" id=status>Status of this document</h2>
 
@@ -14262,12 +14264,13 @@
      attribute is present, then:</p>
 
     <ol>
-     <li>If the <code title=attr-object-type><a href="#type6">type</a></code>
-      attribute is present and its value is not a type that the user agent
-      supports, and is not a type that the user agent can find a handler for,
-      then the user agent may jump to the last step in the overall set of
-      steps (fallback) without downloading the content to examine its real
-      type.
+     <li>
+      <p>If the <code title=attr-object-type><a href="#type6">type</a></code>
+       attribute is present and its value is not a type that the user agent
+       supports, and is not a type that the user agent can find a handler
+       for, then the user agent may jump to the last step in the overall set
+       of steps (fallback) without downloading the content to examine its
+       real type.
 
      <li>
       <p>Begin a load for the resource.</p>

Modified: source
===================================================================
--- source	2008-05-07 00:55:05 UTC (rev 1534)
+++ source	2008-05-07 01:00:25 UTC (rev 1535)
@@ -12266,9 +12266,9 @@
 
     <ol>
 
-     <li>If the <code title="attr-object-type">type</code> attribute
-     is present and its value is not a type that the user agent
-     supports, and is not a type that the user agent can find a
+     <li><p>If the <code title="attr-object-type">type</code>
+     attribute is present and its value is not a type that the user
+     agent supports, and is not a type that the user agent can find a
      handler for, then the user agent may jump to the last step in the
      overall set of steps (fallback) without downloading the content
      to examine its real type.</p></li>




More information about the Commit-Watchers mailing list