[html5] r2265 - [e] (0) remove remaining non-big issue markers

[whatwg at whatwg.org]

Author: ianh
Date: 2008-10-02 03:07:25 -0700 (Thu, 02 Oct 2008)
New Revision: 2265

Modified:
   index
   source
Log:
[e] (0) remove remaining non-big issue markers

Modified: index
===================================================================
--- index	2008-10-02 10:06:03 UTC (rev 2264)
+++ index	2008-10-02 10:07:25 UTC (rev 2265)
@@ -28932,7 +28932,7 @@
 
    <dd><a href=#ignore>Ignore</a> the node.</dd>
 
-  </dl><p class=issue>We should support <code><a href=#the-label-element>label</a></code> in the
+  </dl><p class=big-issue>We should support <code><a href=#the-label-element>label</a></code> in the
   algorithm above -- just iterate through the contents like with
   <code><a href=#the-li-element>li</a></code>, to support <code><a href=#the-input-element>input</a></code> elements in
   <code><a href=#the-label-element>label</a></code> elements. Also, <code><a href=#the-optgroup-element>optgroup</a></code> elements
@@ -35939,7 +35939,7 @@
 };
 
 interface <dfn id=sqlstatementerrorcallback>SQLStatementErrorCallback</dfn> {
-  boolean <span title=dom-sqlstatementerrorcallback-handleEvent>handleEvent</span>(in <a href=#sqltransaction>SQLTransaction</a> transaction, in <a href=#sqlerror>SQLError</a> error);<span class=issue>Or should these arguments be the other way around? Either way we're inconsistent with _something_. What should we be consistent with?</span>
+  boolean <span title=dom-sqlstatementerrorcallback-handleEvent>handleEvent</span>(in <a href=#sqltransaction>SQLTransaction</a> transaction, in <a href=#sqlerror>SQLError</a> error);
 };</pre>
 
   <p>When the <dfn id=dom-sqltransaction-executesql title=dom-sqltransaction-executeSql><code>executeSql(<var title="">sqlStatement</var>, <var title="">arguments</var>, <var title="">callback</var>, <var title="">errorCallback</var>)</code></dfn> method is invoked, the
@@ -38651,7 +38651,7 @@
   void <a href=#dom-dragevent-initdrageventns title=dom-DragEvent-initDragEventNS>initDragEventNS</a>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in <a href=#datatransfer>DataTransfer</a> dataTransferArg);
 };</pre>
 
-  <p class=issue>We should have modifier key information in here too
+  <p class=big-issue>We should have modifier key information in here too
   (shift/ctrl, etc), like with mouse events and like with the context
   menu event.</p>
 

Modified: source
===================================================================
--- source	2008-10-02 10:06:03 UTC (rev 2264)
+++ source	2008-10-02 10:07:25 UTC (rev 2265)
@@ -32594,7 +32594,7 @@
 
   </dl>
 
-  <p class="issue">We should support <code>label</code> in the
+  <p class="big-issue">We should support <code>label</code> in the
   algorithm above -- just iterate through the contents like with
   <code>li</code>, to support <code>input</code> elements in
   <code>label</code> elements. Also, <code>optgroup</code> elements
@@ -40701,7 +40701,7 @@
 };
 
 interface <dfn>SQLStatementErrorCallback</dfn> {
-  boolean <span title="dom-sqlstatementerrorcallback-handleEvent">handleEvent</span>(in <span>SQLTransaction</span> transaction, in <span>SQLError</span> error);<span class="issue">Or should these arguments be the other way around? Either way we're inconsistent with _something_. What should we be consistent with?</span>
+  boolean <span title="dom-sqlstatementerrorcallback-handleEvent">handleEvent</span>(in <span>SQLTransaction</span> transaction, in <span>SQLError</span> error);
 };</pre>
 
   <p>When the <dfn
@@ -43801,7 +43801,7 @@
   void <span title="dom-DragEvent-initDragEventNS">initDragEventNS</span>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in <span>DataTransfer</span> dataTransferArg);
 };</pre>
 
-  <p class="issue">We should have modifier key information in here too
+  <p class="big-issue">We should have modifier key information in here too
   (shift/ctrl, etc), like with mouse events and like with the context
   menu event.</p>