[html5] r3910 - [e] (0) Move 'implements' requirements to IDL.
whatwg at whatwg.org
whatwg at whatwg.org
Sat Sep 19 14:14:57 PDT 2009
Author: ianh
Date: 2009-09-19 14:14:56 -0700 (Sat, 19 Sep 2009)
New Revision: 3910
Modified:
index
source
Log:
[e] (0) Move 'implements' requirements to IDL.
Modified: index
===================================================================
--- index 2009-09-19 10:01:55 UTC (rev 3909)
+++ index 2009-09-19 21:14:56 UTC (rev 3910)
@@ -48299,7 +48299,9 @@
attribute <a href=#function>Function</a> <a href=#handler-window-onunload title=handler-window-onunload>onunload</a>;
attribute <a href=#function>Function</a> <a href=#handler-onvolumechange title=handler-onvolumechange>onvolumechange</a>;
attribute <a href=#function>Function</a> <a href=#handler-onwaiting title=handler-onwaiting>onwaiting</a>;
-};</pre>
+};
+<a href=#window>Window</a> implements <span>EventTarget</span>;
+</pre>
<!-- for more features to add here, look here:
http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/obj_window.asp
@@ -48320,9 +48322,6 @@
</dl><div class=impl>
- <p>The <code><a href=#window>Window</a></code> object must also implement the
- <code>EventTarget</code> interface.</p>
-
<p>The <dfn id=dom-window title=dom-window><code>window</code></dfn>, <dfn id=dom-frames title=dom-frames><code>frames</code></dfn>, and <dfn id=dom-self title=dom-self><code>self</code></dfn> IDL attributes must all
return the <code><a href=#window>Window</a></code> object's <a href=#browsing-context>browsing
context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
@@ -51115,12 +51114,9 @@
<div class=impl>
- <p>Objects implementing the <code><a href=#navigator>Navigator</a></code> interface must
- also implement the <a href=#navigatorid>NavigatorID</a>,
- <a href=#navigatoronline>NavigatorOnLine</a>, and
- <a href=#navigatorabilities>NavigatorAbilities</a> interfaces. (These interfaces are
- defined separately so that other specifications can re-use parts of
- the <code><a href=#navigator>Navigator</a></code> interface.)</p>
+ <p>These interfaces are defined separately so that other
+ specifications can re-use parts of the <code><a href=#navigator>Navigator</a></code>
+ interface.</p>
<!-- v2: also, see window.external.AddSearchProvider() and similar DOM APIs from IE -->
@@ -53169,7 +53165,8 @@
attribute <a href=#function>Function</a> <a href=#handler-appcache-onupdateready title=handler-appcache-onupdateready>onupdateready</a>;
attribute <a href=#function>Function</a> <a href=#handler-appcache-oncached title=handler-appcache-oncached>oncached</a>;
attribute <a href=#function>Function</a> <a href=#handler-appcache-onobsolete title=handler-appcache-onobsolete>onobsolete</a>;
-};</pre>
+};
+<a href=#applicationcache>ApplicationCache</a> implements <span>EventTarget</span>;</pre>
<dl class=domintro><dt><var title="">cache</var> = <var title="">window</var> . <code title=dom-applicationCache><a href=#dom-applicationcache>applicationCache</a></code></dt>
<dd>
@@ -53210,9 +53207,6 @@
</dl><div class=impl>
- <p>Objects implementing the <code><a href=#applicationcache>ApplicationCache</a></code> interface
- must also implement the <code>EventTarget</code> interface.</p>
-
<p>There is a one-to-one mapping from <a href=#cache-host title="cache host">cache
hosts</a> to <code><a href=#applicationcache>ApplicationCache</a></code> objects. The <dfn id=dom-applicationcache title=dom-applicationCache><code>applicationCache</code></dfn>
attribute on <code><a href=#window>Window</a></code> objects must return the
@@ -60591,7 +60585,8 @@
// event handler attributes
attribute <a href=#function>Function</a> <a href=#handler-messageport-onmessage title=handler-MessagePort-onmessage>onmessage</a>;
-};</pre>
+};
+<a href=#messageport>MessagePort</a> implements <span>EventTarget</span>;</pre>
<dl class=domintro><!-- v2-onclose
<dt><var title="">port</var> . <code title="dom-MessagePort-active">active</code></dt>
@@ -60631,9 +60626,6 @@
</dl><div class=impl>
- <p>Objects implementing the <code><a href=#messageport>MessagePort</a></code> interface must
- also implement the <code>EventTarget</code> interface.</p>
-
<p>Each <code><a href=#messageport>MessagePort</a></code> object can be entangled with
another (a symmetric relationship). Each <code><a href=#messageport>MessagePort</a></code>
object also has a <a href=#task-source>task source</a> called the <dfn id=port-message-queue>port
Modified: source
===================================================================
--- source 2009-09-19 10:01:55 UTC (rev 3909)
+++ source 2009-09-19 21:14:56 UTC (rev 3910)
@@ -54466,7 +54466,9 @@
attribute <span>Function</span> <span title="handler-window-onunload">onunload</span>;
attribute <span>Function</span> <span title="handler-onvolumechange">onvolumechange</span>;
attribute <span>Function</span> <span title="handler-onwaiting">onwaiting</span>;
-};</pre>
+};
+<span>Window</span> implements <span>EventTarget</span>;
+</pre>
<!-- for more features to add here, look here:
http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/obj_window.asp
@@ -54491,9 +54493,6 @@
<div class="impl">
- <p>The <code>Window</code> object must also implement the
- <code>EventTarget</code> interface.</p>
-
<p>The <dfn title="dom-window"><code>window</code></dfn>, <dfn
title="dom-frames"><code>frames</code></dfn>, and <dfn
title="dom-self"><code>self</code></dfn> IDL attributes must all
@@ -57766,12 +57765,9 @@
<div class="impl">
- <p>Objects implementing the <code>Navigator</code> interface must
- also implement the <span>NavigatorID</span>,
- <span>NavigatorOnLine</span>, and
- <span>NavigatorAbilities</span> interfaces. (These interfaces are
- defined separately so that other specifications can re-use parts of
- the <code>Navigator</code> interface.)</p>
+ <p>These interfaces are defined separately so that other
+ specifications can re-use parts of the <code>Navigator</code>
+ interface.</p>
<!-- v2: also, see window.external.AddSearchProvider() and similar DOM APIs from IE -->
@@ -60120,7 +60116,8 @@
attribute <span>Function</span> <span title="handler-appcache-onupdateready">onupdateready</span>;
attribute <span>Function</span> <span title="handler-appcache-oncached">oncached</span>;
attribute <span>Function</span> <span title="handler-appcache-onobsolete">onobsolete</span>;
-};</pre>
+};
+<span>ApplicationCache</span> implements <span>EventTarget</span>;</pre>
<dl class="domintro">
@@ -60165,9 +60162,6 @@
<div class="impl">
- <p>Objects implementing the <code>ApplicationCache</code> interface
- must also implement the <code>EventTarget</code> interface.</p>
-
<p>There is a one-to-one mapping from <span title="cache host">cache
hosts</span> to <code>ApplicationCache</code> objects. The <dfn
title="dom-applicationCache"><code>applicationCache</code></dfn>
@@ -70333,11 +70327,9 @@
<!-- v2-onclose attribute <span>Function</span> <span title="handler-WorkerGlobalScope-onclose">onclose</span>;
--> attribute <span>Function</span> <span title="handler-WorkerGlobalScope-onerror">onerror</span>;
};
-<span>WorkerGlobalScope</span> implements <span>WorkerUtils</span>;</pre>
+<span>WorkerGlobalScope</span> implements <span>WorkerUtils</span>;
+<span>WorkerGlobalScope</span> implements <span>EventTarget</span>;</pre>
- <p>Objects implementing the <code>WorkerGlobalScope</code> interface
- must also implement the <code>EventTarget</code> interface.</p>
-
<p>The <dfn
title="dom-WorkerGlobalScope-self"><code>self</code></dfn> attribute
must return the <code>WorkerGlobalScope</code> object itself.</p>
@@ -71082,11 +71074,9 @@
<pre class="idl">interface <dfn>AbstractWorker</dfn> {
attribute <span>Function</span> <span title="handler-AbstractWorker-onerror">onerror</span>;
<!-- v2-onclose attribute <span>Function</span> <span title="handler-AbstractWorker-onclose">onclose</span>; -->
-};</pre>
+};
+<span>AbstractWorker</span> implements <span>EventTarget</span>;</pre>
- <p>Objects implementing the <code>AbstractWorker</code> interface
- must also implement the <code>EventTarget</code> interface.</p>
-
<p>The following are the <span>event handler attributes</span> (and their corresponding <span
title="event handler event type">event handler event types</span>)
that must be supported, as IDL attributes, by objects implementing
@@ -71522,20 +71512,8 @@
void <span title="dom-WorkerGlobalScope-importScripts">importScripts</span>(in DOMString... urls);
readonly attribute <span title="worker-Navigator">Navigator</span> <span title="dom-worker-navigator">navigator</span>;
};
-// implemented by <span>WorkerGlobalScope</span></pre>
+<span>WorkerUtils</span> implement <span>WindowTimers</span>;</pre>
- <p>Objects that implement the <code>WorkerGlobalScope</code>
- interface must also implement the <code>WorkerUtils</code>
- interface.</p>
-
- <p>Objects that implement the <code>WorkerUtils</code> interface
- must also implement the <code>WindowTimers</code> interface. (This
- interface provides the <code
- title="dom-windowtimers-setTimeout">setTimeout()</code> method and
- its friends.)</p>
-
- <hr>
-
<p>The DOM APIs (<code>Node</code> objects, <code>Document</code>
objects, etc) are not available to workers in this version of this
specification.</p>
@@ -71929,12 +71907,9 @@
attribute <span>Function</span> <span title="handler-EventSource-onmessage">onmessage</span>;
attribute <span>Function</span> <span title="handler-EventSource-onerror">onerror</span>;
void <span title="dom-EventSource-close">close</span>();
-};</pre>
+};
+<span>EventSource</span> implements <span>EventTarget</span>;</pre>
- <p><code>EventSource</code> objects must also implement the
- <code>EventTarget</code> interface. <a
- href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
-
<p>The <dfn title="dom-EventSource"><code>EventSource(<var
title="">url</var>)</code></dfn> constructor takes one argument,
<var title="">url</var>, which specifies the <span>URL</span> to
@@ -72689,12 +72664,9 @@
attribute <span>Function</span> <span title="handler-WebSocket-onclose">onclose</span>;
boolean <span title="dom-WebSocket-send">send</span>(in DOMString data);
void <span title="dom-WebSocket-close">close</span>();
-};</pre>
+};
+<span>WebSocket</span> implements <span>EventTarget</span>;</pre>
- <p><code>WebSocket</code> objects must also implement the
- <code>EventTarget</code> interface. <a
- href="#refsDOMEVENTS">[DOMEVENTS]</a>
-
<p>The <dfn title="dom-WebSocket"><code>WebSocket(<var
title="">url</var>, <var title="">protocol</var>)</code></dfn>
constructor takes one or two arguments. The first argument, <var
@@ -75019,7 +74991,8 @@
// event handler attributes
attribute <span>Function</span> <span title="handler-MessagePort-onmessage">onmessage</span>;
-};</pre>
+};
+<span>MessagePort</span> implements <span>EventTarget</span>;</pre>
<dl class="domintro">
<!-- v2-onclose
@@ -75064,9 +75037,6 @@
<div class="impl">
- <p>Objects implementing the <code>MessagePort</code> interface must
- also implement the <code>EventTarget</code> interface.</p>
-
<p>Each <code>MessagePort</code> object can be entangled with
another (a symmetric relationship). Each <code>MessagePort</code>
object also has a <span>task source</span> called the <dfn>port
More information about the Commit-Watchers
mailing list