W3C home > Mailing lists > Public > public-html-commits@w3.org > June 2009

html5/spec Overview.html,1.2429,1.2430

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 16 Jun 2009 19:20:24 +0000
To: public-html-commits@w3.org
Message-Id: <E1MGeCn-00080r-2y@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv30787

Modified Files:
	Overview.html 
Log Message:
WebIDL spelling. (bug 6992) (whatwg r3283)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2429
retrieving revision 1.2430
diff -u -d -r1.2429 -r1.2430
--- Overview.html	16 Jun 2009 19:18:53 -0000	1.2429
+++ Overview.html	16 Jun 2009 19:20:21 -0000	1.2430
@@ -1156,7 +1156,7 @@
   completeness. More approachable tutorials and authoring guides can
   provide a gentler introduction to the topic.<p>In particular, readers should be familiar with the basics of DOM
   Core and DOM Events before reading this specification. An
-  understanding of WebIDL, HTTP, XML, Unicode, character encodings,
+  understanding of Web IDL, HTTP, XML, Unicode, character encodings,
   JavaScript, and CSS will be helpful in places but is not
   essential.<h3 id="scope"><span class="secno">1.3 </span>Scope</h3><p><em>This section is non-normative.</em><p>This specification is limited to providing a semantic-level
   markup language and associated semantic-level scripting APIs for
@@ -1516,7 +1516,7 @@
 
     <p>User agents that support scripting must also be conforming
     implementations of the IDL fragments in this specification, as
-    described in the WebIDL specification. <a href="#references">[WebIDL]</a></p>
+    described in the Web IDL specification. <a href="#references">[WEBIDL]</a></p>
 
    </dd>
 
@@ -1761,13 +1761,13 @@
 
    </dd>
 
-   <dt>WebIDL</dt>
+   <dt>Web IDL</dt>
 
    <dd>
 
     <p>The IDL fragments in this specification must be interpreted as
     required for conforming IDL fragments, as described in the Web IDL
-    specification. <a href="#references">[WebIDL]</a></p>
+    specification. <a href="#references">[WEBIDL]</a></p>
 
     <p>Unless otherwise specified, if a DOM attribute that is a
     floating point number type (<code title="">float</code>) is
@@ -4584,7 +4584,7 @@
   used as the new content attribute value.</p>
 
   <p class="note">The values &plusmn;Infinity and NaN throw an
-  exception on setting, as defined by WebIDL. <a href="#references">[WEBIDL]</a></p>
+  exception on setting, as defined by Web IDL. <a href="#references">[WEBIDL]</a></p>
 
   <p>If a reflecting DOM attribute is of the type
   <code><a href="#domtokenlist-0">DOMTokenList</a></code> or <code><a href="#domsettabletokenlist-0">DOMSettableTokenList</a></code>, then
@@ -4649,7 +4649,7 @@
 
   </div><h5 id="htmlcollection"><span class="secno">2.8.2.1 </span>HTMLCollection</h5><p>The <code><a href="#htmlcollection-0">HTMLCollection</a></code> interface represents a generic
   <a href="#collections-0" title="collections">collection</a> of elements.</p><!-- IE does [Callable] with magic that calls item() or namedItem() as appropriate as if it were a regular [[Get]],
-       so we might need to change this for compat. However, WebIDL doesn't support that for now. --><!-- heycam says we could just say something like "In the ECMAScript binding, host objects that implement interface
+       so we might need to change this for compat. However, Web IDL doesn't support that for now. --><!-- heycam says we could just say something like "In the ECMAScript binding, host objects that implement interface
        <code>HTMLCollection</code> have a [[Call]] method that that behaves as follows: 1. If called with 0 or more than 1
        argument, throw a TypeError. 2. Let arg be the single argument passed. 3. Invoke [[Get]] on the object with ToString(argument)
        as the property name. 4. Return Result(3)." (but we'd have to verify that that's right for 0 and >1 args) --><pre class="idl">[Callable=<a href="#dom-htmlcollection-nameditem" title="dom-HTMLCollection-namedItem">namedItem</a>]
@@ -6222,7 +6222,7 @@
 
     <p class="note">There will be at least one such element, by
     definition.<!-- (If there wasn't, then this algorithm wouldn't
-    have been invoked by WebIDL.) --></p>
+    have been invoked by Web IDL.) --></p>
 
    </li>
 
@@ -7552,7 +7552,7 @@
    <code><a href="#navigator">Navigator</a></code>, and <code><a href="#selection-0">Selection</a></code> objects, the
    various <code><a href="#barprop">BarProp</a></code> objects, the two <code>Storage</code>
    objects, and the various <code><a href="#htmlcollection-0">HTMLCollection</a></code> objects. It
-   also includes all the WebIDL prototypes in the JavaScript binding,
+   also includes all the Web IDL prototypes in the JavaScript binding,
    including the <code>Document</code> object's prototype.)</li>
 
    <!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E...%3Ciframe%20src%3D%22document%22%3E%3C%2Fiframe%3E%0A%3Cscript%3Eonload%20%3D%20function%20()%20%7B%20f%20%3D%20document.getElementsByTagName('iframe')%5B0%5D%3B%20d%20%3D%20f.contentWindow.document%3B%20%7D%3C%2Fscript%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22w(d.documentElement.innerHTML)%22%20value%3D%22dump%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write('%3Cscript%3Evar%20x%20%3D%20new%20XMLHttpRequest()%3Bx.open(%26quot%3BGET%26quot%3B%2C%20%26quot%3BGET%26quot%3B)%3Bx.onreadystatechange%3Dfunction()%20%7B%20alert(x.readyState)%3B%20%7D%3Bx.send(null)%3B%3C%2Fscript%3E')%3Bd.close()%3B%20setTimeout(function()%20%7B%20d.open()%3B%20d.write('%3Cp%3Etest%3C%2Fp%3E')%3B%20d.close()%20%7D%2C%200)%3B%22%20value%3D%22xhr%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.onclick%20%3D%20function()%20%7B%20w('click')%20%7D%22%20value%3D%22add%20click%20handler%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write('%3Cp%3Etest%3C%2Fp%3E')%3B%20d.close()%22%20value%3D%22replace%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write('%3Cp%3E%3Cscript%3Ei%20%3D%200%3B%20setTimeout(%26quot%3Bparent.w(i%2B%2B)%26quot%3B%2C%202000)%3C%2Fscript%3E%3C%2Fp%3E')%3B%20d.close()%22%20value%3D%22replace%20with%20timer%22%3E -->
@@ -40850,7 +40850,7 @@
 
     <p class="note">There will be at least one such element, by
     definition.<!-- (If there wasn't, then this algorithm wouldn't
-    have been invoked by WebIDL.) --></p>
+    have been invoked by Web IDL.) --></p>
 
    </li>
 
@@ -42524,7 +42524,7 @@
 
   </dl></div><h3 id="timers"><span class="secno">6.6 </span>Timers</h3><p>The <code title="dom-windowtimers-setTimeout"><a href="#dom-windowtimers-settimeout">setTimeout()</a></code>
   and <code title="dom-windowtimers-setInterval"><a href="#dom-windowtimers-setinterval">setInterval()</a></code>
-  methods allow authors to schedule timer-based callbacks.</p><!-- HereBeDragons is just meant to prevent this from compiling in random WebIDL implementations --><pre class="idl">[HereBeDragons, NoInterfaceObject] interface <dfn id="windowtimers">WindowTimers</dfn> {
+  methods allow authors to schedule timer-based callbacks.</p><!-- HereBeDragons is just meant to prevent this from compiling in random Web IDL implementations --><pre class="idl">[HereBeDragons, NoInterfaceObject] interface <dfn id="windowtimers">WindowTimers</dfn> {
   long <a href="#dom-windowtimers-settimeout" title="dom-windowtimers-setTimeout">setTimeout</a>(in any handler, [Optional] in any timeout, [Variadic] in any args);
   void <a href="#dom-windowtimers-cleartimeout" title="dom-windowtimers-clearTimeout">clearTimeout</a>(in long handle);
   long <a href="#dom-windowtimers-setinterval" title="dom-windowtimers-setInterval">setInterval</a>(in any handler, [Optional] in any timeout, [Variadic] in any args);
Received on Tuesday, 16 June 2009 19:27:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 16 June 2009 19:27:52 GMT