spec/Overview.html 1.2070 2902 fix errors related to use of class=impl

fix errors related to use of class=impl (credit: sp) (whatwg r2902)

HTMLQuoteElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#htmlquoteelement
coords
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#attr-area-coords
3.6 APIs in HTML documents
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#apis-in-html-documents
rowspan
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#attr-tdth-rowspan
cite
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#attr-blockquote-cite
4.2.3 The base element
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#the-base-element
5.5.4.2 Processing model
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#processing-model-2
toDataURL()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#dom-canvas-todataurl
pause
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#pause
4.2.2 The title element
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#the-title-element
headers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#attr-tdth-headers
hasFeature(feature, version)
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#hasfeature
HTMLTableElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#htmltableelement
Interactive content
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2070.html#interactive-content-0

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2069&r2=1.2070&f=h
http://html5.org/tools/web-apps-tracker?from=2901&to=2902

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2069
retrieving revision 1.2070
diff -u -d -r1.2069 -r1.2070
--- Overview.html 24 Mar 2009 08:45:35 -0000 1.2069
+++ Overview.html 24 Mar 2009 08:57:12 -0000 1.2070
@@ -6023,7 +6023,7 @@
   "<code title="">HTML</code>" and "<code>5.0</code>" (respectively)
   to determine whether or not this module is supported by the
   implementation. In addition to the feature string "<code title="">HTML</code>", the feature string "<code title="">XHTML</code>" (with version string "<code>5.0</code>") can
-  be used to check if the implementation supports XHTML. <span title=impl>User agents should respond with a true value when the
+  be used to check if the implementation supports XHTML. <span class=impl>User agents should respond with a true value when the
   <code><a href=#hasfeature>hasFeature</a></code> method is queried with these values.</span>
   Authors are cautioned, however, that UAs returning true might not be
   perfectly compliant, and that UAs returning false might well have
@@ -7492,7 +7492,7 @@
   behavior</a>, which means that the user can activate them. This
   triggers a sequence of events dependent on the activation mechanism,
   and normally culminating in a <code title=event-click>click</code>
-  event followed by a <code title=event-DOMActivate>DOMActivate</code> event<span title=impl>, as described below</span>.<div class=impl>
+  event followed by a <code title=event-DOMActivate>DOMActivate</code> event<span class=impl>, as described below</span>.<div class=impl>
 
   <p>The user agent should allow the user to manually trigger elements
   that have an <a href=#activation-behavior>activation behavior</a>, for instance using
@@ -7684,7 +7684,7 @@
 
     <p>The canonical form of HTML markup is all-lowercase; thus, this
     method will <a href=#converted-to-lowercase title="converted to lowercase">lowercase</a>
-    the argument before creating the requisite element. <span title=impl>Also, the element created must be in the <a href=#html-namespace-0>HTML
+    the argument before creating the requisite element. <span class=impl>Also, the element created must be in the <a href=#html-namespace-0>HTML
     namespace</a></span>.</p>
 
     <p class=note>This doesn't apply to <code title="">Document.createElementNS()</code>. Thus, it is possible,
@@ -8516,7 +8516,7 @@
   &lt;h1&gt;The Dances&lt;/h1&gt;</pre>
 
   </div><p>The string to use as the document's title is given by the <code title=dom-document-title><a href=#document.title>document.title</a></code> DOM
-  attribute. <span title=impl>User agents should use the document's
+  attribute. <span class=impl>User agents should use the document's
   title when referring to the document in their user
   interface.</span><h4 id=the-base-element><span class=secno>4.2.3 </span>The <dfn><code>base</code></dfn> element</h4><dl class=element><dt>Categories</dt>
    <dd><a href=#metadata-content-0>Metadata content</a>.</dd>
@@ -11372,7 +11372,7 @@
   another source, whose address, if it has one, should be cited in the
   <dfn id=attr-blockquote-cite title=attr-blockquote-cite><code>cite</code></dfn>
   attribute.<p>If the <code title=attr-blockquote-cite><a href=#attr-blockquote-cite>cite</a></code> attribute
-  is present, it must be a <a href=#valid-url>valid URL</a>. <span title=impl>To obtain the corresponding citation link, the value of
+  is present, it must be a <a href=#valid-url>valid URL</a>. <span class=impl>To obtain the corresponding citation link, the value of
   the attribute must be <a href=#resolve-a-url title="resolve a url">resolved</a>
   relative to the element. User agents should allow users to follow
   such citation links.</span><div class=impl>
@@ -19103,7 +19103,7 @@
 
   </div><table><thead><tr><th> Type <th> Other arguments
    <tbody><tr><td> image/jpeg
-     <td> The second argument<span title=impl>, if it</span> is a
+     <td> The second argument<span class=impl>, if it</span> is a
      number between 0.0 and 1.0<span class=impl>, must be</span>
      treated as the desired quality level. <span class=impl>If it is
      not a number or is outside that range, the user agent must use
@@ -21741,7 +21741,7 @@
   attribute must, if specified, contain a <a href=#valid-list-of-integers>valid list of
   integers</a>. This attribute gives the coordinates for the shape
   described by the <code title=attr-area-shape><a href=#attr-area-shape>shape</a></code>
-  attribute. <span title=impl>The processing for this attribute is
+  attribute. <span class=impl>The processing for this attribute is
   described as part of the <a href=#image-map>image map</a> processing
   model.</span></p><!-- v2: It was suggested by John S. Urban that coords should
   support percentages as well as pixels, so that one could use the
@@ -22182,7 +22182,7 @@
   encouraged to find heuristics to determine which tables actually
   contain data and which are merely being used for layout. This
   specification does not define a precise heuristic.<p>Tables have rows and columns given by their descendants. A table
-  must not have an empty row or column<span title=impl>, as
+  must not have an empty row or column<span class=impl>, as
   described in the description of the <a href=#table-model>table
   model</a></span>. <!-- conformance criteria for detecting this
   are in the table model section --><div class=impl>
@@ -22934,7 +22934,7 @@
   attribute specified, whose value must be a <a href=#valid-non-negative-integer>valid non-negative
   integer</a>.<p>These attributes give the number of columns and rows respectively
   that the cell is to span. These attributes must not be used to
-  overlap cells<span title=impl>, as described in the description of
+  overlap cells<span class=impl>, as described in the description of
   the <a href=#table-model>table model</a></span>.</p><!-- conformance criteria
   for determining when this is violated are given in the processing
   model --><hr><p>The <code><a href=#the-td-element>td</a></code> and <code><a href=#the-th-element>th</a></code> element may have a <dfn id=attr-tdth-headers title=attr-tdth-headers><code>headers</code></dfn> content
@@ -35918,10 +35918,10 @@
    <li><p>Return to the first step of the <a href=#event-loop>event
    loop</a>.</li>
 
-  </ol><hr><p class=impl>Some of the algorithms in this specification, for
-  historical reasons, require the user agent to <dfn id=pause>pause</dfn> while
-  running a <a href=#concept-task title=concept-task>task</a> until some
-  condition has been met. While a user agent has a paused <a href=#concept-task title=concept-task>task</a>, the corresponding <a href=#event-loop>event
+  </ol><hr><p>Some of the algorithms in this specification, for historical
+  reasons, require the user agent to <dfn id=pause>pause</dfn> while running a
+  <a href=#concept-task title=concept-task>task</a> until some condition has been
+  met. While a user agent has a paused <a href=#concept-task title=concept-task>task</a>, the corresponding <a href=#event-loop>event
   loop</a> must not run further <a href=#concept-task title=concept-task>tasks</a>, and any script in the currently
   running <a href=#concept-task title=concept-task>task</a> must block. User
   agents should remain responsive to user input while paused, however,

Received on Tuesday, 24 March 2009 08:59:47 UTC