Commits

annevk committed ec1b2b9 Draft

IDL renamed type to name

Comments (0)

Files changed (3)

 <!--end-logo-->
 </div>
  <h1>DOM4</h1>
- <h2 class="no-num no-toc" id="editor's-draft-7-june-2012">
-  <span class="w3conly">Editor's Draft 7 June 2012</span>
+ <h2 class="no-num no-toc" id="editor's-draft-21-june-2012">
+  <span class="w3conly">Editor's Draft 21 June 2012</span>
   </h2>
 
  <dl>
   <ol class="toc">
    <li><a href="#exception-domexception"><span class="secno">3.1 </span>Exception <code>DOMException</code></a></li>
    <li><a href="#interface-domerror"><span class="secno">3.2 </span>Interface <code>DOMError</code></a></li>
-   <li><a href="#error-types-0"><span class="secno">3.3 </span>Error types</a></ol></li>
+   <li><a href="#error-names-0"><span class="secno">3.3 </span>Error names</a></ol></li>
  <li><a href="#events"><span class="secno">4 </span>Events</a>
   <ol class="toc">
    <li><a href="#introduction-to-dom-events"><span class="secno">4.1 </span>Introduction to "DOM Events"</a></li>
 field must return the value it was initialized to. When an exception is
 created it must be initialized to zero.
 
-<p>To <dfn id="concept-throw" title="concept-throw">throw</dfn> a <var title="">type</var> exception
+<p>To <dfn id="concept-throw" title="concept-throw">throw</dfn> a <var title="">name</var> exception
 these steps must be run:
 
 <ol>
  <li><p>Create a new <code><a href="#domexception">DOMException</a></code> exception whose
- <a class="external" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-type">type</a> is <var title="">type</var>.
+ <a class="external" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-name">name</a> is <var title="">name</var>.
 
  <li><p>Set its <a class="external" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-message">message</a> to a
  user agent-defined value.
 
- <li><p>If its <a class="external" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-type">type</a> is in the first
- column of the <a href="#error-types-table">error types table</a> and has a corresponding legacy
+ <li><p>If its <a class="external" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-name">name</a> is in the first
+ column of the <a href="#error-names-table">error names table</a> and has a corresponding legacy
  <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code> exception field value in the
  third column, set its <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code>
  exception field to that value.
 <p class="example">To
 <i title="">throw a "<code><a href="#timeouterror">TimeoutError</a></code>" exception</i>, a
 user agent would construct a <code><a href="#domexception">DOMException</a></code> exception whose
-<a class="external" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-type">type</a> is
+<a class="external" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-name">name</a> is
 "<code><a href="#timeouterror">TimeoutError</a></code>" and
 <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code> exception field value is 23,
 and actually throw that object as an exception. In JavaScript, this
 
 <p class="note">This interface is intended for other specifications that want
 to introduce error handling through other means than exceptions. As with
-exceptions, the <a href="#error-types-table">error types table</a> is used.
+exceptions, the <a href="#error-names-table">error names table</a> is used.
 
 <pre class="idl">interface <dfn id="domerror">DOMError</dfn> {
   readonly attribute DOMString <a href="#dom-domerror-name" title="dom-DOMError-name">name</a>;
 return the value it was initialized to.
 
 <p>A
-<dfn id="concept-domerror" title="concept-DOMError"><var title="">type</var> <code>DOMError</code></dfn>
+<dfn id="concept-domerror" title="concept-DOMError"><var title="">name</var> <code>DOMError</code></dfn>
 means a <code><a href="#domerror">DOMError</a></code> object whose
 <code title="dom-DOMError-name"><a href="#dom-domerror-name">name</a></code> attribute is initialized to
-<var title="">type</var>.
+<var title="">name</var>.
 
 <p class="example">A specification could say that an <code title="">error</code>
 attribute must return a
 <a href="#concept-domerror" title="concept-DOMError">"<code>SyntaxError</code>" <code>DOMError</code></a>.
 
 
-<h3 id="error-types-0"><span class="secno">3.3 </span>Error types</h3>
-
-<p>The <dfn id="error-types-table">error types table</dfn> below lists all the allowed error types,
+<h3 id="error-names-0"><span class="secno">3.3 </span>Error names</h3>
+
+<p>The <dfn id="error-names-table">error names table</dfn> below lists all the allowed error names,
 a description, and legacy <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code>
-exception field values (when the error type is used for
+exception field values (when the error name is used for
 <a href="#concept-throw" title="concept-throw">throwing</a> an exception).
 
-<p class="note">If your specification requires an error type not listed here,
+<p class="note">If your specification requires an error name not listed here,
 please file a bug as indicated at the top of this specification and it will
 be addressed shortly. Thanks!
 
-<table id="error-types">
+<table id="error-names">
  <thead>
- <tr><th>Type<th>Description<th>Legacy <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code> exception field value (if any)
+ <tr><th>Name<th>Description<th>Legacy <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code> exception field value (if any)
  <tbody>
  <tr>
   <td>"<dfn id="indexsizeerror"><code>IndexSizeError</code></dfn>"

Overview.src.html

 field must return the value it was initialized to. When an exception is
 created it must be initialized to zero.
 
-<p>To <dfn title=concept-throw>throw</dfn> a <var title>type</var> exception
+<p>To <dfn title=concept-throw>throw</dfn> a <var title>name</var> exception
 these steps must be run:
 
 <ol>
  <li><p>Create a new <code>DOMException</code> exception whose
- <span data-anolis-spec=webidl>type</span> is <var title>type</var>.
+ <span data-anolis-spec=webidl>name</span> is <var title>name</var>.
 
  <li><p>Set its <span data-anolis-spec=webidl>message</span> to a
  user agent-defined value.
 
- <li><p>If its <span data-anolis-spec=webidl>type</span> is in the first
- column of the <span>error types table</span> and has a corresponding legacy
+ <li><p>If its <span data-anolis-spec=webidl>name</span> is in the first
+ column of the <span>error names table</span> and has a corresponding legacy
  <code title=dom-DOMException-code>code</code> exception field value in the
  third column, set its <code title=dom-DOMException-code>code</code>
  exception field to that value.
 <p class=example>To
 <i title>throw a "<code>TimeoutError</code>" exception</i>, a
 user agent would construct a <code>DOMException</code> exception whose
-<span data-anolis-spec=webidl>type</span> is
+<span data-anolis-spec=webidl>name</span> is
 "<code>TimeoutError</code>" and
 <code title=dom-DOMException-code>code</code> exception field value is 23,
 and actually throw that object as an exception. In JavaScript, this
 
 <p class=note>This interface is intended for other specifications that want
 to introduce error handling through other means than exceptions. As with
-exceptions, the <span>error types table</span> is used.
+exceptions, the <span>error names table</span> is used.
 
 <pre class=idl>interface <dfn>DOMError</dfn> {
   readonly attribute DOMString <span title=dom-DOMError-name>name</span>;
 return the value it was initialized to.
 
 <p>A
-<dfn title=concept-DOMError><var title>type</var> <code>DOMError</code></dfn>
+<dfn title=concept-DOMError><var title>name</var> <code>DOMError</code></dfn>
 means a <code>DOMError</code> object whose
 <code title=dom-DOMError-name>name</code> attribute is initialized to
-<var title>type</var>.
+<var title>name</var>.
 
 <p class=example>A specification could say that an <code title>error</code>
 attribute must return a
 <span title=concept-DOMError>"<code>SyntaxError</code>" <code>DOMError</code></span>.
 
 
-<h3>Error types</h3>
-
-<p>The <dfn>error types table</dfn> below lists all the allowed error types,
+<h3>Error names</h3>
+
+<p>The <dfn>error names table</dfn> below lists all the allowed error names,
 a description, and legacy <code title=dom-DOMException-code>code</code>
-exception field values (when the error type is used for
+exception field values (when the error name is used for
 <span title=concept-throw>throwing</span> an exception).
 
-<p class=note>If your specification requires an error type not listed here,
+<p class=note>If your specification requires an error name not listed here,
 please file a bug as indicated at the top of this specification and it will
 be addressed shortly. Thanks!
 
-<table id=error-types>
+<table id=error-names>
  <thead>
- <tr><th>Type<th>Description<th>Legacy <code title=dom-DOMException-code>code</code> exception field value (if any)
+ <tr><th>Name<th>Description<th>Legacy <code title=dom-DOMException-code>code</code> exception field value (if any)
  <tbody>
  <tr>
   <td>"<dfn><code>IndexSizeError</code></dfn>"
 
 <div class="head">
 <h1>DOM4</h1>
- <h2 class="no-num no-toc" id="free-editor's-draft-7-june-2012">
-  <span class="now3c">Free Editor's Draft 7 June 2012</span>
+ <h2 class="no-num no-toc" id="free-editor's-draft-21-june-2012">
+  <span class="now3c">Free Editor's Draft 21 June 2012</span>
  </h2>
 
  <dl>
 <p class="now3c copyright"><a href="http://creativecommons.org/publicdomain/zero/1.0/" rel="license"><img alt="CC0" src="http://i.creativecommons.org/p/zero/1.0/80x15.png"></a>
 To the extent possible under law, the editors have waived all copyright and
 related or neighboring rights to this work. In addition, as of
-7 June 2012, the editors have made this specification available
+21 June 2012, the editors have made this specification available
 under the
 <a href="http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0" rel="license">Open Web Foundation Agreement Version 1.0</a>,
 which is available at
   <ol>
    <li><a href="#exception-domexception"><span class="secno">3.1 </span>Exception <code>DOMException</code></a></li>
    <li><a href="#interface-domerror"><span class="secno">3.2 </span>Interface <code>DOMError</code></a></li>
-   <li><a href="#error-types-0"><span class="secno">3.3 </span>Error types</a></ol></li>
+   <li><a href="#error-names-0"><span class="secno">3.3 </span>Error names</a></ol></li>
  <li><a href="#events"><span class="secno">4 </span>Events</a>
   <ol>
    <li><a href="#introduction-to-dom-events"><span class="secno">4.1 </span>Introduction to "DOM Events"</a></li>
 field must return the value it was initialized to. When an exception is
 created it must be initialized to zero.
 
-<p>To <dfn id="concept-throw" title="concept-throw">throw</dfn> a <var title="">type</var> exception
+<p>To <dfn id="concept-throw" title="concept-throw">throw</dfn> a <var title="">name</var> exception
 these steps must be run:
 
 <ol>
  <li><p>Create a new <code><a href="#domexception">DOMException</a></code> exception whose
- <a class="external" data-anolis-spec="webidl" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-type">type</a> is <var title="">type</var>.
+ <a class="external" data-anolis-spec="webidl" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-name">name</a> is <var title="">name</var>.
 
  <li><p>Set its <a class="external" data-anolis-spec="webidl" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-message">message</a> to a
  user agent-defined value.
 
- <li><p>If its <a class="external" data-anolis-spec="webidl" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-type">type</a> is in the first
- column of the <a href="#error-types-table">error types table</a> and has a corresponding legacy
+ <li><p>If its <a class="external" data-anolis-spec="webidl" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-name">name</a> is in the first
+ column of the <a href="#error-names-table">error names table</a> and has a corresponding legacy
  <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code> exception field value in the
  third column, set its <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code>
  exception field to that value.
 <p class="example">To
 <i title="">throw a "<code><a href="#timeouterror">TimeoutError</a></code>" exception</i>, a
 user agent would construct a <code><a href="#domexception">DOMException</a></code> exception whose
-<a class="external" data-anolis-spec="webidl" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-type">type</a> is
+<a class="external" data-anolis-spec="webidl" href="http://dev.w3.org/2006/webapi/WebIDL/#dfn-exception-name">name</a> is
 "<code><a href="#timeouterror">TimeoutError</a></code>" and
 <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code> exception field value is 23,
 and actually throw that object as an exception. In JavaScript, this
 
 <p class="note">This interface is intended for other specifications that want
 to introduce error handling through other means than exceptions. As with
-exceptions, the <a href="#error-types-table">error types table</a> is used.
+exceptions, the <a href="#error-names-table">error names table</a> is used.
 
 <pre class="idl">interface <dfn id="domerror">DOMError</dfn> {
   readonly attribute DOMString <a href="#dom-domerror-name" title="dom-DOMError-name">name</a>;
 return the value it was initialized to.
 
 <p>A
-<dfn id="concept-domerror" title="concept-DOMError"><var title="">type</var> <code>DOMError</code></dfn>
+<dfn id="concept-domerror" title="concept-DOMError"><var title="">name</var> <code>DOMError</code></dfn>
 means a <code><a href="#domerror">DOMError</a></code> object whose
 <code title="dom-DOMError-name"><a href="#dom-domerror-name">name</a></code> attribute is initialized to
-<var title="">type</var>.
+<var title="">name</var>.
 
 <p class="example">A specification could say that an <code title="">error</code>
 attribute must return a
 <a href="#concept-domerror" title="concept-DOMError">"<code>SyntaxError</code>" <code>DOMError</code></a>.
 
 
-<h3 id="error-types-0"><span class="secno">3.3 </span>Error types</h3>
-
-<p>The <dfn id="error-types-table">error types table</dfn> below lists all the allowed error types,
+<h3 id="error-names-0"><span class="secno">3.3 </span>Error names</h3>
+
+<p>The <dfn id="error-names-table">error names table</dfn> below lists all the allowed error names,
 a description, and legacy <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code>
-exception field values (when the error type is used for
+exception field values (when the error name is used for
 <a href="#concept-throw" title="concept-throw">throwing</a> an exception).
 
-<p class="note">If your specification requires an error type not listed here,
+<p class="note">If your specification requires an error name not listed here,
 please file a bug as indicated at the top of this specification and it will
 be addressed shortly. Thanks!
 
-<table id="error-types">
+<table id="error-names">
  <thead>
- <tr><th>Type<th>Description<th>Legacy <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code> exception field value (if any)
+ <tr><th>Name<th>Description<th>Legacy <code title="dom-DOMException-code"><a href="#dom-domexception-code">code</a></code> exception field value (if any)
  <tbody>
  <tr>
   <td>"<dfn id="indexsizeerror"><code>IndexSizeError</code></dfn>"