Skip to content

Commit

Permalink
Remove event path monkey patch
Browse files Browse the repository at this point in the history
The DOM Standard (finally) defines that Window is at the top of the event path when a Document has
an associated browsing context and the event’s type is not “load”.

See whatwg/dom@2d7b637 for details.
  • Loading branch information
annevk committed Feb 18, 2016
1 parent ec1dc4d commit dad854e
Showing 1 changed file with 0 additions and 18 deletions.
18 changes: 0 additions & 18 deletions source
Expand Up @@ -86500,24 +86500,6 @@ interface <dfn>WindowEventHandlers</dfn> {
</div>


<div w-nodev>

<h5>Events and the <code>Window</code> object</h5>

<p>When an event is dispatched at a DOM node in a <code>Document</code> that has a <span
data-x="concept-document-bc">browsing context</span>, if the event is not a <code
data-x="event-load">load</code> event, the user agent must act as if, for the purposes of <span
data-x="concept-event-dispatch">event dispatching</span>, the <code>Window</code> object is the
parent of the <code>Document</code> object. <ref spec=DOM></p>

<!-- If Anne does this: http://krijnhoetmer.nl/irc-logs/whatwg/20121205#l-4 (see bug 18780)
<p>If a <code>Document</code> object is associated with a <code>Window</code> object, its
<span>event parent</span> is that <code>Window</code> object.</p>
-->

</div>


<h3 id="atob">Base64 utility methods</h3>

<p>The <code data-x="dom-windowbase64-atob">atob()</code> and <code
Expand Down

0 comments on commit dad854e

Please sign in to comment.