Skip to content

Commit

Permalink
[e] (0) Fix minor mistakes in recent checkins.
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.whatwg.org/webapps@2689 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jan 21, 2009
1 parent f2d6f58 commit f17cb4a
Show file tree
Hide file tree
Showing 2 changed files with 30 additions and 10 deletions.
20 changes: 15 additions & 5 deletions index
Expand Up @@ -10521,12 +10521,22 @@ not-slash = %x0000-002E / %x0030-%10FFFF
elements</a>.</p>

<p class=example>Thus, for example, a bubbling <code title=event-message><a href=#event-message>message</a></code> event fired on a child of
<a href=#the-body-element-1>the body element</a> of a <code>Document</code> would
<a href=#the-body-element-1>the body element</a> of a <code>Document</code> would first
trigger the <code title=handler-onmessage><a href=#handler-onmessage>onmessage</a></code>
<a href=#event-handler-content-attributes>event handler content attributes</a> of that element and of
the root <code><a href=#the-html-element>html</a></code> element, but would not trigger the <code title=handler-window-onmessage><a href=#handler-window-onmessage>onmessage</a></code> <a href=#event-handler-content-attributes title="event
<a href=#event-handler-content-attributes>event handler content attributes</a> of that element, then
that of the root <code><a href=#the-html-element>html</a></code> element, and only <em>then</em>
would it trigger the <code title=handler-window-onmessage><a href=#handler-window-onmessage>onmessage</a></code> <a href=#event-handler-content-attributes title="event
handler content attributes">event handler content attribute</a>
on the <code><a href=#the-body-element>body</a></code> element.</p>
on the <code><a href=#the-body-element>body</a></code> element. This is because the event would
bubble from the target, to the <code><a href=#the-body-element>body</a></code>, to the
<code><a href=#the-html-element>html</a></code>, to the <code>Document</code>, to the
<code><a href=#window>Window</a></code>, and the event handler attribute on the
<code><a href=#the-body-element>body</a></code> is watching the <code><a href=#window>Window</a></code> not the
<code><a href=#the-body-element>body</a></code>. A regular event listener attached to the
<code><a href=#the-body-element>body</a></code> using <code title="">addEventListener()</code>,
however, would fire when the event bubbled through the
<code><a href=#the-body-element>body</a></code> and not when it reaches the <code><a href=#window>Window</a></code>
object.</p>


<h4 id=the-section-element><span class=secno>4.4.2 </span>The <dfn><code>section</code></dfn> element</h4>
Expand Down Expand Up @@ -35425,7 +35435,7 @@ interface <dfn id=function>Function</dfn> {
<dl><dt><dfn id=handler-window-onbeforeunload title=handler-window-onbeforeunload><code>onbeforeunload</code></dfn></dt>

<dd><p>Must be invoked whenever a <code title=event-beforeunload>beforeunload</code> event is targeted at or bubbles
through the element or object.</dd>
through the object.</dd>

<dt><dfn id=handler-window-onerror title=handler-window-onerror><code>onerror</code></dfn></dt>

Expand Down
20 changes: 15 additions & 5 deletions source
Expand Up @@ -11182,13 +11182,23 @@ not-slash = %x0000-002E / %x0030-%10FFFF

<p class="example">Thus, for example, a bubbling <code
title="event-message">message</code> event fired on a child of
<span>the body element</span> of a <code>Document</code> would
<span>the body element</span> of a <code>Document</code> would first
trigger the <code title="handler-onmessage">onmessage</code>
<span>event handler content attributes</span> of that element and of
the root <code>html</code> element, but would not trigger the <code
<span>event handler content attributes</span> of that element, then
that of the root <code>html</code> element, and only <em>then</em>
would it trigger the <code
title="handler-window-onmessage">onmessage</code> <span title="event
handler content attributes">event handler content attribute</span>
on the <code>body</code> element.</p>
on the <code>body</code> element. This is because the event would
bubble from the target, to the <code>body</code>, to the
<code>html</code>, to the <code>Document</code>, to the
<code>Window</code>, and the event handler attribute on the
<code>body</code> is watching the <code>Window</code> not the
<code>body</code>. A regular event listener attached to the
<code>body</code> using <code title="">addEventListener()</code>,
however, would fire when the event bubbled through the
<code>body</code> and not when it reaches the <code>Window</code>
object.</p>


<h4>The <dfn><code>section</code></dfn> element</h4>
Expand Down Expand Up @@ -40309,7 +40319,7 @@ interface <dfn>Function</dfn> {

<dd><p>Must be invoked whenever a <code
title="event-beforeunload">beforeunload</code> event is targeted at or bubbles
through the element or object.</p></dd>
through the object.</p></dd>

<dt><dfn title="handler-window-onerror"><code>onerror</code></dfn></dt>

Expand Down

0 comments on commit f17cb4a

Please sign in to comment.