[html5] r818 - /

whatwg at whatwg.org whatwg at whatwg.org
Tue May 15 18:28:01 PDT 2007


Author: ianh
Date: 2007-05-15 18:28:00 -0700 (Tue, 15 May 2007)
New Revision: 818

Modified:
   index
   source
Log:
[] (0) Define some error handling for methods and attributes passed NaN, Inf, etc values.

Modified: index
===================================================================
--- index	2007-05-16 01:20:43 UTC (rev 817)
+++ index	2007-05-16 01:28:00 UTC (rev 818)
@@ -143,10 +143,13 @@
      <li><a href="#conformance"><span class=secno>1.3. </span>Conformance
       requirements</a>
       <ul class=toc>
-       <li><a href="#dependencies"><span class=secno>1.3.1.
+       <li><a href="#common"><span class=secno>1.3.1. </span>Common
+        conformance requirements for APIs</a>
+
+       <li><a href="#dependencies"><span class=secno>1.3.2.
         </span>Dependencies</a>
 
-       <li><a href="#features"><span class=secno>1.3.2. </span>Features
+       <li><a href="#features"><span class=secno>1.3.3. </span>Features
         defined in other specifications</a>
       </ul>
 
@@ -175,7 +178,7 @@
         content attributes in DOM attributes</a>
       </ul>
 
-     <li><a href="#common"><span class=secno>2.3. </span>Common DOM
+     <li><a href="#common0"><span class=secno>2.3. </span>Common DOM
       interfaces</a>
       <ul class=toc>
        <li><a href="#collections"><span class=secno>2.3.1.
@@ -224,10 +227,10 @@
      <li><a href="#semantics-intro"><span class=secno>3.1.
       </span>Introduction</a>
 
-     <li><a href="#common0"><span class=secno>3.2. </span>Common
+     <li><a href="#common1"><span class=secno>3.2. </span>Common
       microsyntaxes</a>
       <ul class=toc>
-       <li><a href="#common1"><span class=secno>3.2.1. </span>Common parser
+       <li><a href="#common2"><span class=secno>3.2.1. </span>Common parser
         idioms</a>
 
        <li><a href="#boolean"><span class=secno>3.2.2. </span>Boolean
@@ -1969,13 +1972,36 @@
    element would be used as well.</p>
   <!-- XXX unexpandable entities? -->
 
+  <h4 id=common><span class=secno>1.3.1. </span>Common conformance
+   requirements for APIs</h4>
+
   <p class=big-issue>A lot of arrays/lists/<span>collection</span>s in this
    spec assume zero-based indexes but use the term "<var
    title="">index</var>th" liberally. We should define those to be zero-based
    and be clearer about this.
 
-  <h4 id=dependencies><span class=secno>1.3.1. </span>Dependencies</h4>
+  <p>Unless other specified, if a DOM attribute that is a floating point
+   number type (<code title="">float</code>) is assigned an Infinity or
+   Not-a-Number value, a <code title=big-issue>NOT_SUPPORTED_ERR</code>
+   exception must be raised.
 
+  <p>Unless other specified, if a DOM attribute that is a signed numberic
+   type is assigned a negative value, a <code
+   title=big-issue>NOT_SUPPORTED_ERR</code> exception must be raised.
+
+  <p>Unless other specified, if a method with an argument that is a floating
+   point number type (<code title="">float</code>) is passed an Infinity or
+   Not-a-Number value, a <code title=big-issue>NOT_SUPPORTED_ERR</code>
+   exception must be raised.
+
+  <p>Unless other specified, if a method is passed a different number of
+   arguments than is defined for that method in its IDL definition, a <code
+   title=big-issue>NOT_SUPPORTED_ERR</code> exception must be raised.
+
+  <p class=big-issue>Anything else? Passing the wrong type of object, maybe?
+
+  <h4 id=dependencies><span class=secno>1.3.2. </span>Dependencies</h4>
+
   <p>This specification relies on several other underlying specifications.
 
   <dl>
@@ -2028,7 +2054,7 @@
    protocol, and several features assume that those languages and protocols
    are in use.
 
-  <h4 id=features><span class=secno>1.3.2. </span>Features defined in other
+  <h4 id=features><span class=secno>1.3.3. </span>Features defined in other
    specifications</h4>
 
   <p>Some elements are defined in terms of their DOM <dfn
@@ -2666,7 +2692,7 @@
    attribute. Otherwise, the DOM attribute must be set to the empty string.</p>
   <!-- XXX or raise an exception? -->
 
-  <h3 id=common><span class=secno>2.3. </span>Common DOM interfaces</h3>
+  <h3 id=common0><span class=secno>2.3. </span>Common DOM interfaces</h3>
 
   <h4 id=collections><span class=secno>2.3.1. </span>Collections</h4>
 
@@ -3965,7 +3991,7 @@
 
   <p class=big-issue>An introduction to marking up a document.
 
-  <h3 id=common0><span class=secno>3.2. </span>Common microsyntaxes</h3>
+  <h3 id=common1><span class=secno>3.2. </span>Common microsyntaxes</h3>
 
   <p>There are various places in HTML that accept particular data types, such
    as dates or numbers. This section describes what the conformance criteria
@@ -3977,7 +4003,7 @@
    attribute values are clearly defined either in terms of microsyntaxes or
    in terms of other specs, or as "Text" or some such.
 
-  <h4 id=common1><span class=secno>3.2.1. </span>Common parser idioms</h4>
+  <h4 id=common2><span class=secno>3.2.1. </span>Common parser idioms</h4>
 
   <p>The <dfn id=space title="space character">space characters</dfn>, for
    the purposes of this specification, are U+0020 SPACE, U+0009 CHARACTER
@@ -23895,7 +23921,7 @@
    title=concept-uda-input>input</a> being the address of the page
    represented by the associated <code>Document</code> object, as an absolute
    IRI reference (same as the <code title=dom-location-href><a
-   href="#href5">href</a></code> attribute), and the <a href="#common2"
+   href="#href5">href</a></code> attribute), and the <a href="#common3"
    title=concept-uda-setter>common setter action</a> being the same as
    setting the <code title=dom-location-href><a href="#href5">href</a></code>
    attribute to the new output value.</p>
@@ -25173,7 +25199,7 @@
   <p>In addition, an interface with a complement of URI decomposition
    attributes will define an <dfn id=input
    title=concept-uda-input>input</dfn>, which is a URI that the attributes
-   act on, and a <dfn id=common2 title=concept-uda-setter>common setter
+   act on, and a <dfn id=common3 title=concept-uda-setter>common setter
    action</dfn>, which is a set of steps invoked when any of the attributes'
    setters are invoked.
 
@@ -25198,7 +25224,7 @@
    title=concept-uda-input>input</a> URI with the new value; otherwise, the
    user agent must let <var title="">output</var> be equal to the <a
    href="#input" title=concept-uda-input>input</a>. Finally, the user agent
-   must invoke the <a href="#common2" title=concept-uda-setter>common setter
+   must invoke the <a href="#common3" title=concept-uda-setter>common setter
    action</a> with the value of <var title="">output</var>.
 
   <p>The rules for parsing and constructing URIs are described in RFC 2396 as

Modified: source
===================================================================
--- source	2007-05-16 01:20:43 UTC (rev 817)
+++ source	2007-05-16 01:28:00 UTC (rev 818)
@@ -448,10 +448,37 @@
   well.</p> <!-- XXX unexpandable entities? -->
 
 
+  <h4>Common conformance requirements for APIs</h4>
+
   <p class="big-issue">A lot of arrays/lists/<span>collection</span>s
   in this spec assume zero-based indexes but use the term "<var
   title="">index</var>th" liberally. We should define those to be
   zero-based and be clearer about this.</p>
+
+  <p>Unless other specified, if a DOM attribute that is a floating
+  point number type (<code title="">float</code>) is assigned an
+  Infinity or Not-a-Number value, a <code
+  title="big-issue">NOT_SUPPORTED_ERR</code> exception must be
+  raised.</p>
+
+  <p>Unless other specified, if a DOM attribute that is a signed
+  numberic type is assigned a negative value, a <code
+  title="big-issue">NOT_SUPPORTED_ERR</code> exception must be
+  raised.</p>
+
+  <p>Unless other specified, if a method with an argument that is a
+  floating point number type (<code title="">float</code>) is passed
+  an Infinity or Not-a-Number value, a <code
+  title="big-issue">NOT_SUPPORTED_ERR</code> exception must be
+  raised.</p>
+
+  <p>Unless other specified, if a method is passed a different number
+  of arguments than is defined for that method in its IDL definition,
+  a <code title="big-issue">NOT_SUPPORTED_ERR</code> exception must be
+  raised.</p>
+
+  <p class="big-issue">Anything else? Passing the wrong type of
+  object, maybe?</p>
   
 
   <h4>Dependencies</h4>




More information about the Commit-Watchers mailing list