Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[e] (0) remove remaining non-big issue markers
git-svn-id: http://svn.whatwg.org/webapps@2265 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Oct 2, 2008
1 parent 7e22b3a commit 01f1862
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
6 changes: 3 additions & 3 deletions index
Expand Up @@ -28932,7 +28932,7 @@ menu li:not(:first-child)::before { content: ' | '; }</pre>

<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
Expand Down Expand Up @@ -35939,7 +35939,7 @@ interface <dfn id=sqlstatementcallback>SQLStatementCallback</dfn> {
};

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
Expand Down Expand Up @@ -38651,7 +38651,7 @@ http://developer.apple.com/documentation/AppleApplications/Conceptual/SafariJSPr
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>

Expand Down
6 changes: 3 additions & 3 deletions source
Expand Up @@ -32594,7 +32594,7 @@ menu li:not(:first-child)::before { content: ' | '; }</pre>

</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
Expand Down Expand Up @@ -40701,7 +40701,7 @@ interface <dfn>SQLStatementCallback</dfn> {
};

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
Expand Down Expand Up @@ -43801,7 +43801,7 @@ http://developer.apple.com/documentation/AppleApplications/Conceptual/SafariJSPr
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>

Expand Down

0 comments on commit 01f1862

Please sign in to comment.