W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2011

hixie: move the 'onerror' stuff up to script execution and away from the no-more-related events stuff (whatwg r5827)

From: poot <cvsmail@w3.org>
Date: Thu, 03 Feb 2011 16:29:34 -0500
To: public-html-diffs@w3.org
Message-Id: <E1Pl6k9-0001M9-VR@jay.w3.org>
hixie: move the 'onerror' stuff up to script execution and away from the
no-more-related events stuff (whatwg r5827)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4682&r2=1.4683&f=h
http://html5.org/tools/web-apps-tracker?from=5826&to=5827

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4682
retrieving revision 1.4683
diff -u -d -r1.4682 -r1.4683
--- Overview.html	3 Feb 2011 21:15:25 -0000	1.4682
+++ Overview.html	3 Feb 2011 21:28:20 -0000	1.4683
@@ -1056,7 +1056,8 @@
        <li><a href="#definitions-0"><span class="secno">6.1.3.1 </span>Definitions</a></li>
        <li><a href="#calling-scripts"><span class="secno">6.1.3.2 </span>Calling scripts</a></li>
        <li><a href="#creating-scripts"><span class="secno">6.1.3.3 </span>Creating scripts</a></li>
-       <li><a href="#killing-scripts"><span class="secno">6.1.3.4 </span>Killing scripts</a></ol></li>
+       <li><a href="#killing-scripts"><span class="secno">6.1.3.4 </span>Killing scripts</a></li>
+       <li><a href="#runtime-script-errors"><span class="secno">6.1.3.5 </span>Runtime script errors</a></ol></li>
      <li><a href="#event-loops"><span class="secno">6.1.4 </span>Event loops</a>
       <ol>
        <li><a href="#definitions-1"><span class="secno">6.1.4.1 </span>Definitions</a></li>
@@ -1068,8 +1069,7 @@
        <li><a href="#event-handler-attributes"><span class="secno">6.1.6.1 </span>Event handlers</a></li>
        <li><a href="#event-handlers-on-elements-document-objects-and-window-objects"><span class="secno">6.1.6.2 </span>Event handlers on elements, <code>Document</code> objects, and <code>Window</code> objects</a></li>
        <li><a href="#event-firing"><span class="secno">6.1.6.3 </span>Event firing</a></li>
-       <li><a href="#events-and-the-window-object"><span class="secno">6.1.6.4 </span>Events and the <code>Window</code> object</a></li>
-       <li><a href="#runtime-script-errors"><span class="secno">6.1.6.5 </span>Runtime script errors</a></ol></ol></li>
+       <li><a href="#events-and-the-window-object"><span class="secno">6.1.6.4 </span>Events and the <code>Window</code> object</a></ol></ol></li>
    <li><a href="#atob"><span class="secno">6.2 </span>Base64 utility methods</a></li>
    <li><a href="#timers"><span class="secno">6.3 </span>Timers</a></li>
    <li><a href="#user-prompts"><span class="secno">6.4 </span>User prompts</a>
@@ -47896,6 +47896,53 @@
 
   </div><div class="impl">
 
+  <h5 id="runtime-script-errors"><span class="secno">6.1.3.5 </span>Runtime script errors</h5>
+
+  <p>Whenever an uncaught runtime script error occurs in one of the
+  scripts associated with a <code><a href="#document">Document</a></code>, the user agent must
+  <a href="#report-the-error">report the error</a> using the <code title="handler-window-onerror"><a href="#handler-window-onerror">onerror</a></code> <a href="#event-handlers" title="event
+  handlers">event handler</a> of the <a href="#script-s-global-object">script's global
+  object</a>. If the error is still <i title="concept-error-nothandled"><a href="#concept-error-nothandled">not handled</a></i> after this, then
+  the error may be reported to the user.</p>
+
+  <hr><p>When the user agent is required to <dfn id="report-the-error" title="report the
+  error">report an error</dfn> <var title="">error</var> using the
+  <a href="#event-handlers" title="event handlers">event handler</a> <var title="">onerror</var>, it must run these steps, after which the
+  error is either <dfn id="concept-error-handled" title="concept-error-handled"><i>handled</i></dfn> or <dfn id="concept-error-nothandled" title="concept-error-nothandled"><i>not handled</i></dfn>:</p>
+
+  <dl class="switch"><dt>If the value of <var title="">onerror</var> is a
+   <code><a href="#function">Function</a></code></dt>
+
+   <dd>
+
+    <p>The function must be invoked with three arguments. The three
+    arguments passed to the function are all <code>DOMString</code>s;
+    the first must give the message that the UA is considering
+    reporting, the second must give the <a href="#absolute-url">absolute URL</a> of
+    the resource in which the error occurred, and the third must give
+    the line number in that resource on which the error occurred.</p>
+
+    <p>If the function returns false, then the error is <i title="concept-error-handled"><a href="#concept-error-handled">handled</a></i>. Otherwise, the error is
+    <i title="concept-error-nothandled"><a href="#concept-error-nothandled">not handled</a></i>.</p>
+
+    <p>Any uncaught exceptions thrown or errors caused by this
+    function may be reported to the user immediately after the error
+    that the function was called for; the <a href="#report-the-error" title="report the
+    error">report an error</a> algorithm must not be used to handle
+    exceptions thrown or errors caused by this function.</p>
+
+   </dd>
+
+   <dt>Otherwise</dt>
+
+   <dd>
+
+    <p>The error is <i title="concept-error-nothandled"><a href="#concept-error-nothandled">not handled</a></i>.</p>
+
+   </dd>
+
+  </dl></div><div class="impl">
+
   <h4 id="event-loops"><span class="secno">6.1.4 </span>Event loops</h4>
 
   <h5 id="definitions-1"><span class="secno">6.1.4.1 </span>Definitions</h5>
@@ -48679,57 +48726,7 @@
    has been prevented, again as if the <code><a href="#window">Window</a></code> object was
    the parent of the <code><a href="#document">Document</a></code> in the dispatch chain.</li>
 
-  </ol></div><div class="impl">
-
-  <h5 id="runtime-script-errors"><span class="secno">6.1.6.5 </span>Runtime script errors</h5>
-
-  <p><i>This section only applies to user agents that support
-  scripting in general and JavaScript in particular.</i></p>
-
-  <p>Whenever an uncaught runtime script error occurs in one of the
-  scripts associated with a <code><a href="#document">Document</a></code>, the user agent must
-  <a href="#report-the-error">report the error</a> using the <code title="handler-window-onerror"><a href="#handler-window-onerror">onerror</a></code> <a href="#event-handlers" title="event
-  handlers">event handler</a> of the <a href="#script-s-global-object">script's global
-  object</a>. If the error is still <i title="concept-error-nothandled"><a href="#concept-error-nothandled">not handled</a></i> after this, then
-  the error may be reported to the user.</p>
-
-  <hr><p>When the user agent is required to <dfn id="report-the-error" title="report the
-  error">report an error</dfn> <var title="">error</var> using the
-  <a href="#event-handlers" title="event handlers">event handler</a> <var title="">onerror</var>, it must run these steps, after which the
-  error is either <dfn id="concept-error-handled" title="concept-error-handled"><i>handled</i></dfn> or <dfn id="concept-error-nothandled" title="concept-error-nothandled"><i>not handled</i></dfn>:</p>
-
-  <dl class="switch"><dt>If the value of <var title="">onerror</var> is a
-   <code><a href="#function">Function</a></code></dt>
-
-   <dd>
-
-    <p>The function must be invoked with three arguments. The three
-    arguments passed to the function are all <code>DOMString</code>s;
-    the first must give the message that the UA is considering
-    reporting, the second must give the <a href="#absolute-url">absolute URL</a> of
-    the resource in which the error occurred, and the third must give
-    the line number in that resource on which the error occurred.</p>
-
-    <p>If the function returns false, then the error is <i title="concept-error-handled"><a href="#concept-error-handled">handled</a></i>. Otherwise, the error is
-    <i title="concept-error-nothandled"><a href="#concept-error-nothandled">not handled</a></i>.</p>
-
-    <p>Any uncaught exceptions thrown or errors caused by this
-    function may be reported to the user immediately after the error
-    that the function was called for; the <a href="#report-the-error" title="report the
-    error">report an error</a> algorithm must not be used to handle
-    exceptions thrown or errors caused by this function.</p>
-
-   </dd>
-
-   <dt>Otherwise</dt>
-
-   <dd>
-
-    <p>The error is <i title="concept-error-nothandled"><a href="#concept-error-nothandled">not handled</a></i>.</p>
-
-   </dd>
-
-  </dl></div><h3 id="atob"><span class="secno">6.2 </span>Base64 utility methods</h3><p>The <code title="dom-windowbase64-atob"><a href="#dom-windowbase64-atob">atob()</a></code> and <code title="dom-windowbase64-btoa"><a href="#dom-windowbase64-btoa">btoa()</a></code> methods allow authors to
+  </ol></div><h3 id="atob"><span class="secno">6.2 </span>Base64 utility methods</h3><p>The <code title="dom-windowbase64-atob"><a href="#dom-windowbase64-atob">atob()</a></code> and <code title="dom-windowbase64-btoa"><a href="#dom-windowbase64-btoa">btoa()</a></code> methods allow authors to
   transform content to and from the base64 encoding.</p><!-- v2: actual binary support --><pre class="idl">[Supplemental, NoInterfaceObject]
 interface <dfn id="windowbase64">WindowBase64</dfn> {
   DOMString <a href="#dom-windowbase64-btoa" title="dom-windowbase64-btoa">btoa</a>(in DOMString btoa);
Received on Thursday, 3 February 2011 21:29:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 February 2011 21:29:42 GMT