[html5] r3129 - [] (0) Mention what happens to event handlers on <body> elements obtained by XHR [...]

Mon May 25 18:17:12 PDT 2009

Author: ianh
Date: 2009-05-25 18:17:11 -0700 (Mon, 25 May 2009)
New Revision: 3129

Modified:
   index
   source
Log:
[] (0) Mention what happens to event handlers on <body> elements obtained by XHR or createDocument(). (bug 6515)

Modified: index
===================================================================

--- index	2009-05-26 01:00:04 UTC (rev 3128)
+++ index	2009-05-26 01:17:11 UTC (rev 3129)
@@ -47754,6 +47754,17 @@
   getting, must return whatever the current value of the corresponding
   event handler attribute is (possibly null).</p>
 
+  <p>If an <a href=#event-handler-dom-attributes title="event handler DOM attributes">event handler
+  DOM attribute</a> exposes an <a href=#event-handler-attributes-0 title="event handler
+  attributes">event handler attribute</a> of an object that doesn't
+  exist, it must always return null on getting and must do nothing on
+  setting.</p>
+
+  <p class=note>This can happen in particular for <a href=#event-handler-dom-attributes title="event
+  handler DOM attributes">event handler DOM attribute</a> on
+  <code><a href=#the-body-element>body</a></code> elements that do not have corresponding
+  <code><a href=#window>Window</a></code> objects.</p>
+
   <p class=note>Certain event handler DOM attributes have additional
   requirements, in particular the <code title=handler-MessagePort-onmessage><a href=#handler-messageport-onmessage>onmessage</a></code> attribute of
   <code><a href=#messageport>MessagePort</a></code> objects.</p>
@@ -47806,8 +47817,8 @@
    </li>
 
    <li><p>If the previous steps failed to compile the script, then set
-   the corresponding <a href=#event-handler-attributes-0 title="event handler attributes">event handler attribute</a> to null and
-   abort these steps.</li>
+   the corresponding <a href=#event-handler-attributes-0 title="event handler attributes">event
+   handler attribute</a> to null and abort these steps.</li>
 
    <li><p>Set up the <a href="#script's-global-object">script's global object</a>, the
    <a href="#script's-browsing-context">script's browsing context</a>, the <a href="#script's-url-character-encoding">script's URL

Modified: source
===================================================================
--- source	2009-05-26 01:00:04 UTC (rev 3128)
+++ source	2009-05-26 01:17:11 UTC (rev 3129)
@@ -54413,6 +54413,17 @@
   getting, must return whatever the current value of the corresponding
   event handler attribute is (possibly null).</p>
 
+  <p>If an <span title="event handler DOM attributes">event handler
+  DOM attribute</span> exposes an <span title="event handler
+  attributes">event handler attribute</span> of an object that doesn't
+  exist, it must always return null on getting and must do nothing on
+  setting.</p>
+
+  <p class="note">This can happen in particular for <span title="event
+  handler DOM attributes">event handler DOM attribute</span> on
+  <code>body</code> elements that do not have corresponding
+  <code>Window</code> objects.</p>
+
   <p class="note">Certain event handler DOM attributes have additional
   requirements, in particular the <code
   title="handler-MessagePort-onmessage">onmessage</code> attribute of
@@ -54482,8 +54493,8 @@
    </li>
 
    <li><p>If the previous steps failed to compile the script, then set
-   the corresponding <span title="event handler attributes">event handler attribute</span> to null and
-   abort these steps.</p></li>
+   the corresponding <span title="event handler attributes">event
+   handler attribute</span> to null and abort these steps.</p></li>
 
    <li><p>Set up the <span>script's global object</span>, the
    <span>script's browsing context</span>, the <span>script's URL


