Skip to content
This repository has been archived by the owner on Mar 19, 2018. It is now read-only.

Commit

Permalink
Add Event.getSupportedListenerOptions
Browse files Browse the repository at this point in the history
Addresses feature detection (issue #8).
  • Loading branch information
RByers committed Jul 3, 2015
1 parent 775caf5 commit 976d101
Showing 1 changed file with 19 additions and 0 deletions.
19 changes: 19 additions & 0 deletions EventListenerOptions.html
Original file line number Diff line number Diff line change
Expand Up @@ -148,6 +148,25 @@ <h2>Extensions to the <code>EventTarget</code> interface</h2>
</dd>
</dl>
</section>
<section>
<h2>Extensions to the <code>Event</code> interface</h2>
<p><code>Event</code> is defined in [[!DOM4]].</p>
<pre class="idl">
partial interface Event {
static EventListenerOptions getSupportedListenerOptions();
};
</pre>
<dl dfn-for="Event">
<dt><dfn>getSupportedListenerOptions</dfn></dt>
<dd>
<p>Return an <a>EventListenerOptions</a> with all dictionary members present.
The values in the dictionary have no meaning.</p>

This comment has been minimized.

Copy link
@tdresser

tdresser Jul 3, 2015

Collaborator

Is a dictionary where the members have no meaning superior to a list of all legal keys for the dictionary?

This comment has been minimized.

Copy link
@RByers

RByers Jul 3, 2015

Author Member

I think this is worthy of some debate. Filed #10.

<p class="note">This API is necessary for feature detection of support
for <code>EventListenerOptions</code> and for any possible future options.
</p>
</dd>
</dl>
</section>
<section class="informative">
<h2>Examples</h2>
<p>The following are examples that demonstrate how the APIs in this specification might
Expand Down

0 comments on commit 976d101

Please sign in to comment.