Skip to content

Commit

Permalink
[giow] (2) postMessage() should fire on the window, not the document
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.whatwg.org/webapps@1491 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Apr 27, 2008
1 parent d4694dc commit eccc9df
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 14 deletions.
11 changes: 4 additions & 7 deletions index
Original file line number Diff line number Diff line change
Expand Up @@ -38537,13 +38537,10 @@ data:&nbsp;test</pre>
value, etc</p>

<li>
<p>Dispatch the event created in the previous step at the <var
title="">target</var> document.</p>
<!-- XXX define this in terms
of the event queue -->
<p class=big-isue>Should we instead make this an event that bubbles and
fire it at the 'body' element? It seems inconsistent to make it fire on
document... Opinions?</p>
<p>Dispatch the event created in the previous step at the <code><a
href="#window">Window</a></code> object on which the method was invoked.</p>
<!-- XXX define this in terms of the event queue -->
<!-- XXX apply any body/window dispatch decisions here -->
</ol>

<p class=warning>Authors should check the <code
Expand Down
11 changes: 4 additions & 7 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -36079,13 +36079,10 @@ data:&nbsp;test</pre>

<li>

<p>Dispatch the event created in the previous step at the <var
title="">target</var> document.</p> <!-- XXX define this in terms
of the event queue -->

<p class="big-isue">Should we instead make this an event that
bubbles and fire it at the 'body' element? It seems inconsistent
to make it fire on document... Opinions?</p>
<p>Dispatch the event created in the previous step at the
<code>Window</code> object on which the method was invoked.</p>
<!-- XXX define this in terms of the event queue -->
<!-- XXX apply any body/window dispatch decisions here -->

</li>

Expand Down

0 comments on commit eccc9df

Please sign in to comment.