ISSUE-131: Previous change removed a note about load not propagating to the defaultView. However, that change by itself does not accurately reflect the behavior implemented. So I reinstated the note but clarified that this only applies to load events fired on elements:
Note: for legacy reasons, load events on elements do not include the defaultView in the propagation path in HTML implementations. See [HTML5] for more information.
--- a/html/DOM3-Events.html Wed Aug 17 08:48:39 2011 +0900
+++ b/html/DOM3-Events.html Wed Aug 17 09:27:57 2011 +0900
@@ -2025,6 +2025,8 @@
</tr>
</table>
<p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when the DOM implementation finishes loading the resource (such as the document) and any dependent resources (such as images, style sheets, or scripts). Dependent resources that fail to load must not prevent this event from firing if the resource that loaded them is still accessible via the DOM. If this event type is dispatched, implementations are required to dispatch this event at least on the <code>Document</code> node.</p>
+ <span class="note" id="_4"><strong>Note:</strong> for legacy reasons, <a class="eventtype" href="#event-type-load"><code>load</code></a> events on elements do not include the <a class="def" href="#glossary-defaultView">defaultView</a> in the propagation path in HTML implementations. See [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>] for more information.</span></p>
+
<!-- This event differs from the <a class="eventtype" href="#event-type-DOMContentLoaded"><code>DOMContentLoaded</code></a> event in that it is not dispatched until all external resources are loaded. -->
</dd>
</dl>