- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 14 Jan 2009 03:34:01 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv9435
Modified Files:
Overview.html
Log Message:
Update IDL blocks to use NoInterfaceObject and ImplementedOn=... appropriately. (whatwg r2661)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1830
retrieving revision 1.1831
diff -u -d -r1.1830 -r1.1831
--- Overview.html 14 Jan 2009 02:38:33 -0000 1.1830
+++ Overview.html 14 Jan 2009 03:33:59 -0000 1.1831
@@ -4916,7 +4916,7 @@
<code>SVGDocument</code>.<p class=note>Because the <code><a href=#htmldocument>HTMLDocument</a></code> interface is
now obtained using binding-specific casting methods instead of
simply being the primary interface of the document object, it is no
- longer defined as inheriting from <code>Document</code>.<pre class=idl>[<a href=#dom-document-nameditem title=dom-document-namedItem>NameGetter</a>=OverrideBuiltins]<!-- XXX http://krijnhoetmer.nl/irc-logs/whatwg/20090113#l-300 -->
+ longer defined as inheriting from <code>Document</code>.<pre class=idl>[<a href=#dom-document-nameditem title=dom-document-namedItem>NameGetter</a>=OverrideBuiltins, ImplementedOn=<span>Document</span>]
interface <dfn id=htmldocument>HTMLDocument</dfn> {
// <a href=#resource-metadata-management>resource metadata management</a>
[PutForwards=href] readonly attribute <a href=#location>Location</a> <a href=#dom-document-location title=dom-document-location>location</a>;
@@ -27118,7 +27118,7 @@
</ol><h3 id=the-default-view><span class=secno>5.2 </span>The default view</h3><p>The <code>AbstractView</code> object of <a href=#default-view title="default
view">default views</a> must also implement the
- <code><a href=#window>Window</a></code> and <code>EventTarget</code> interfaces.<pre class=idl>[NoInterfaceObject, <a href=#dom-window-item title=dom-window-item>IndexGetter</a>, <a href=#dom-window-nameditem title=dom-window-namedItem>NameGetter</a>=OverrideBuiltins]
+ <code><a href=#window>Window</a></code> and <code>EventTarget</code> interfaces.<pre class=idl>[<a href=#dom-window-item title=dom-window-item>IndexGetter</a>, <a href=#dom-window-nameditem title=dom-window-namedItem>NameGetter</a>=OverrideBuiltins]
interface <dfn id=window>Window</dfn> {
// the current browsing context
readonly attribute <a href=#window>Window</a> <a href=#dom-window title=dom-window>window</a>;
@@ -28824,7 +28824,7 @@
called. The new auxiliary browsing context has no name.</p>
<p class=note>This browsing context implements the
- <code><a href=#modalwindow>ModalWindow</a></code> interface.</p>
+ <code><a href=#windowmodal>WindowModal</a></code> interface.</p>
</li>
@@ -28874,14 +28874,16 @@
</li>
</ol><p>Browsing contexts created by the above algorithm must implement
- the <code><a href=#modalwindow>ModalWindow</a></code> interface:<pre class=idl>[XXX] interface <dfn id=modalwindow>ModalWindow</dfn> {
- readonly attribute any <a href=#dom-modalwindow-dialogarguments title=dom-modalWindow-dialogArguments>dialogArguments</a>;
- attribute DOMString <a href=#dom-modalwindow-returnvalue title=dom-modalWindow-returnValue>returnValue</a>;
+ the <code><a href=#windowmodal>WindowModal</a></code> interface:<p class=XXX>Really I want the Window object to just gain these
+ attributes, as if they were on the Window prototype. That's the XXX
+ below.<pre class=idl>[NoInterfaceObject, ImplementedOn=<a href=#window>Window</a>, XXX] interface <dfn id=windowmodal>WindowModal</dfn> {
+ readonly attribute any <a href=#dom-windowmodal-dialogarguments title=dom-WindowModal-dialogArguments>dialogArguments</a>;
+ attribute DOMString <a href=#dom-windowmodal-returnvalue title=dom-WindowModal-returnValue>returnValue</a>;
};</pre><p>Such browsing contexts have associated <dfn id=dialog-arguments>dialog
arguments</dfn>, which are stored along with the <dfn id=dialog-arguments-origin>dialog
arguments' origin</dfn>. These values are set by the <code title=dom-showModalDialog><a href=#dom-showmodaldialog>showModalDialog()</a></code> method in the
algorithm above, when the browsing context is created, based on the
- arguments provided to the method.<p>The <dfn id=dom-modalwindow-dialogarguments title=dom-modalWindow-dialogArguments><code>dialogArguments</code></dfn>
+ arguments provided to the method.<p>The <dfn id=dom-windowmodal-dialogarguments title=dom-WindowModal-dialogArguments><code>dialogArguments</code></dfn>
DOM attribute, on getting, must check whether its browsing context's
<a href=#active-document>active document</a>'s <a href=#origin-0>origin</a> is the <a href=#same-origin title="same origin">same</a> as the <a href=#dialog-arguments-origin>dialog arguments'
origin</a>. If it is, then the browsing context's <a href=#dialog-arguments>dialog
@@ -28894,7 +28896,7 @@
<p>These browsing contexts also have an associated <dfn id=return-value>return
value</dfn>. The <a href=#return-value>return value</a> of a browsing context
must be initialized to the empty string when the browsing context is
- created.<p>The <dfn id=dom-modalwindow-returnvalue title=dom-modalWindow-returnValue><code>returnValue</code></dfn>
+ created.<p>The <dfn id=dom-windowmodal-returnvalue title=dom-WindowModal-returnValue><code>returnValue</code></dfn>
DOM attribute, on getting, must return the <a href=#return-value>return value</a>
of its browsing context, and on setting, must set the <a href=#return-value>return
value</a> to the given new value.<p class=note>The <code title=dom-window-close><a href=#dom-window-close>window.close()</a></code> method can be used to
@@ -29102,7 +29104,7 @@
// objects implementing this interface also implement the interfaces given below
};
-[NoInterfaceObject] interface <dfn id=navigatorid>NavigatorID</dfn> {<!--
+[NoInterfaceObject, ImplementedOn=<a href=#navigator>Navigator</a>] interface <dfn id=navigatorid>NavigatorID</dfn> {<!--
readonly attribute DOMString <span title="dom-navigator-appCodeName">appCodeName</span>;-->
readonly attribute DOMString <a href=#dom-navigator-appname title=dom-navigator-appName>appName</a>;
readonly attribute DOMString <a href=#dom-navigator-appversion title=dom-navigator-appVersion>appVersion</a>;
@@ -29110,11 +29112,11 @@
readonly attribute DOMString <a href=#dom-navigator-useragent title=dom-navigator-userAgent>userAgent</a>;
};
-[NoInterfaceObject] interface <dfn id=navigatoronline>NavigatorOnLine</dfn> {
+[NoInterfaceObject, ImplementedOn=<a href=#navigator>Navigator</a>] interface <dfn id=navigatoronline>NavigatorOnLine</dfn> {
readonly attribute boolean <a href=#dom-navigator-online title=dom-navigator-onLine>onLine</a>;
};
-[NoInterfaceObject] interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
+[NoInterfaceObject, ImplementedOn=<a href=#navigator>Navigator</a>] interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
// content handler registration
void <a href=#dom-navigator-registerprotocolhandler title=dom-navigator-registerProtocolHandler>registerProtocolHandler</a>(in DOMString protocol, in DOMString url, in DOMString title);
void <a href=#dom-navigator-registercontenthandler title=dom-navigator-registerContentHandler>registerContentHandler</a>(in DOMString mimeType, in DOMString url, in DOMString title);
@@ -35326,7 +35328,7 @@
<code><a href=#the-eventsource-element>eventsource</a></code> element provides a simple interface to
this mechanism.<h4 id=the-remoteeventtarget-interface><span class=secno>7.2.1 </span>The <code><a href=#remoteeventtarget>RemoteEventTarget</a></code> interface</h4><p>Any object that implements the <code>EventTarget</code> interface
must also implement the <code><a href=#remoteeventtarget>RemoteEventTarget</a></code>
- interface.<pre class=idl>interface <dfn id=remoteeventtarget>RemoteEventTarget</dfn> {
+ interface.<pre class=idl>[NoInterfaceObject, ImplementedOn=<span>EventTarget</span>] interface <dfn id=remoteeventtarget>RemoteEventTarget</dfn> {
void <a href=#dom-remoteeventtarget-addeventsource title=dom-RemoteEventTarget-addEventSource>addEventSource</a>(in DOMString src);
void <a href=#dom-remoteeventtarget-removeeventsource title=dom-RemoteEventTarget-removeEventSource>removeEventSource</a>(in DOMString src);
};</pre><p>When the <dfn id=dom-remoteeventtarget-addeventsource title=dom-RemoteEventTarget-addEventSource><code>addEventSource(<var title="">src</var>)</code></dfn> method is invoked, the user agent
@@ -35697,8 +35699,7 @@
underlying network. For example, this interface could not be used to
implement an IRC client without proxying messages through a custom
server.<p class=XXX>An introduction to the client-side and
- server-side of using the direct connection APIs.</p><!--BOILERPLATE--><h4 id=the-websocket-interface><span class=secno>7.3.2 </span>The <code><a href=#websocket>WebSocket</a></code> interface</h4><pre class=idl>
-[<a href=#dom-websocket title=dom-WebSocket>Constructor</a>(in DOMString url)]
+ server-side of using the direct connection APIs.</p><!--BOILERPLATE--><h4 id=the-websocket-interface><span class=secno>7.3.2 </span>The <code><a href=#websocket>WebSocket</a></code> interface</h4><pre class=idl>[<a href=#dom-websocket title=dom-WebSocket>Constructor</a>(in DOMString url)]
interface <dfn id=websocket>WebSocket</dfn> {
readonly attribute DOMString <a href=#dom-websocket-url title=dom-WebSocket-URL>URL</a>;
@@ -45554,7 +45555,7 @@
or technologies based on X3D that are namespace-aware.</p><!-- <p>XXX example here</p> --><h3 id=timers><span class=secno>11.4 </span>Timers</h3><p class=XXX>This section is expected to be moved to its own
specification in due course. It needs a lot of work to actually make
it into a semi-decent spec.<p>Objects that implement the <code><a href=#window>Window</a></code> interface must
- also implement the <code><a href=#windowtimers>WindowTimers</a></code> interface:<pre class=idl>[NoInterfaceObject] interface <dfn id=windowtimers>WindowTimers</dfn> {
+ also implement the <code><a href=#windowtimers>WindowTimers</a></code> interface:<pre class=idl>[NoInterfaceObject, ImplementedOn=<a href=#window>Window</a>] interface <dfn id=windowtimers>WindowTimers</dfn> {
// timers
long <a href=#dom-windowtimers-settimeout title=dom-windowtimers-setTimeout>setTimeout</a>(in <a href=#timeouthandler>TimeoutHandler</a> handler, in long timeout);
long <a href=#dom-windowtimers-settimeout title=dom-windowtimers-setTimeout>setTimeout</a>(in <a href=#timeouthandler>TimeoutHandler</a> handler, in long timeout, <var title="">arguments...</var>);
@@ -45610,7 +45611,7 @@
<i>frozen</i>.<h3 id=rendering-and-the-dom><span class=secno>11.5 </span>Rendering and the DOM</h3><p class=XXX>This section is expected to be moved to its own
specification in due course. It needs a lot of work to actually make
it into a semi-decent spec.<p>Any object implement the <code>AbstractView</code> interface must
- also implement the <code><a href=#mediamodeabstractview>MediaModeAbstractView</a></code> interface.<pre class=idl>interface <dfn id=mediamodeabstractview>MediaModeAbstractView</dfn> {
+ also implement the <code><a href=#mediamodeabstractview>MediaModeAbstractView</a></code> interface.<pre class=idl>[NoInterfaceObject, ImplementedOn=<span>AbstractView</span>] interface <dfn id=mediamodeabstractview>MediaModeAbstractView</dfn> {
readonly attribute DOMString <a href=#mediamode>mediaMode</a>;
};</pre><p>The <dfn id=mediamode><code>mediaMode</code></dfn> attribute on objects
implementing the <code><a href=#mediamodeabstractview>MediaModeAbstractView</a></code> interface must
Received on Wednesday, 14 January 2009 03:34:14 UTC