Skip to content

Commit

Permalink
[e] (0) accuracy
Browse files Browse the repository at this point in the history
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13822

git-svn-id: http://svn.whatwg.org/webapps@6625 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Oct 4, 2011
1 parent c77fd96 commit 19da6fb
Show file tree
Hide file tree
Showing 3 changed files with 28 additions and 63 deletions.
29 changes: 9 additions & 20 deletions complete.html
Expand Up @@ -3260,10 +3260,10 @@ <h4 id=scripting-0><span class=secno>2.1.4 </span>Scripting</h4>
data.</p>

<p>In the contexts of events, the terms <dfn title="">fire</dfn> and
<dfn title="">dispatch</dfn> are used as defined in the DOM Core
specification: firing an event means to create and dispatch it, and
dispatching an event means to follow the steps that propagate the
event through the tree. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used to refer
<dfn id=concept-event-dispatch title=concept-event-dispatch>dispatch</dfn> are used as
defined in the DOM Core specification: firing an event means to
create and dispatch it, and dispatching an event means to follow the
steps that propagate the event through the tree. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used to refer
to events that have the <span>trusted flag</span> set. <a href=#refsDOMCORE>[DOMCORE]</a></p>


Expand Down Expand Up @@ -37808,9 +37808,7 @@ <h6 id=pixel-manipulation><span class=secno>4.8.11.1.11 </span><dfn>Pixel manipu
wholesale, with no composition, alpha blending, no shadows,
etc.</p>

<p>If the first argument is null, throws a
<code><a href=#typemismatcherror>TypeMismatchError</a></code> exception. Throws a
<code><a href=#notsupportederror>NotSupportedError</a></code> exception if any of the other
<p>Throws a <code><a href=#notsupportederror>NotSupportedError</a></code> exception if any of the
arguments are not finite.</p>

</dd>
Expand Down Expand Up @@ -69308,20 +69306,11 @@ <h5 id=events-and-the-window-object><span class=secno>7.1.6.4 </span>Events and
<p>When an event is dispatched at a DOM node in a
<code><a href=#document>Document</a></code> in a <a href=#browsing-context>browsing context</a>, if the
event is not a <code title=event-load>load</code> event, the user
agent must also dispatch the event to the <code><a href=#window>Window</a></code>, as
follows:</p>

<ol><li>In the capture phase, the event must propagate to the
<code><a href=#window>Window</a></code> object before propagating to any of the nodes,
as if the <code><a href=#window>Window</a></code> object was the parent of the
<code><a href=#document>Document</a></code> in the dispatch chain.</li>

<li>In the bubble phase, the event must propagate up to the
<code><a href=#window>Window</a></code> object at the end of the phase, unless bubbling
has been prevented, again as if the <code><a href=#window>Window</a></code> object was
the parent of the <code><a href=#document>Document</a></code> in the dispatch chain.</li>
agent must act as if, for the purposes of <a href=#concept-event-dispatch title=concept-event-dispatch>event dispatching</a>, the
<code><a href=#window>Window</a></code> object is the parent of the
<code><a href=#document>Document</a></code> object. <a href=#refsDOMCORE>[DOMCORE]</a></p>

</ol></div>
</div>


<h3 id=atob><span class=secno>7.2 </span>Base64 utility methods</h3>
Expand Down
29 changes: 9 additions & 20 deletions index
Expand Up @@ -3260,10 +3260,10 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
data.</p>

<p>In the contexts of events, the terms <dfn title="">fire</dfn> and
<dfn title="">dispatch</dfn> are used as defined in the DOM Core
specification: firing an event means to create and dispatch it, and
dispatching an event means to follow the steps that propagate the
event through the tree. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used to refer
<dfn id=concept-event-dispatch title=concept-event-dispatch>dispatch</dfn> are used as
defined in the DOM Core specification: firing an event means to
create and dispatch it, and dispatching an event means to follow the
steps that propagate the event through the tree. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used to refer
to events that have the <span>trusted flag</span> set. <a href=#refsDOMCORE>[DOMCORE]</a></p>


Expand Down Expand Up @@ -37808,9 +37808,7 @@ v6DVT (also check for '- -' bits in the part above) --><p>The <dfn id=dom-contex
wholesale, with no composition, alpha blending, no shadows,
etc.</p>

<p>If the first argument is null, throws a
<code><a href=#typemismatcherror>TypeMismatchError</a></code> exception. Throws a
<code><a href=#notsupportederror>NotSupportedError</a></code> exception if any of the other
<p>Throws a <code><a href=#notsupportederror>NotSupportedError</a></code> exception if any of the
arguments are not finite.</p>

</dd>
Expand Down Expand Up @@ -69308,20 +69306,11 @@ interface <dfn id=function>Function</dfn> {
<p>When an event is dispatched at a DOM node in a
<code><a href=#document>Document</a></code> in a <a href=#browsing-context>browsing context</a>, if the
event is not a <code title=event-load>load</code> event, the user
agent must also dispatch the event to the <code><a href=#window>Window</a></code>, as
follows:</p>

<ol><li>In the capture phase, the event must propagate to the
<code><a href=#window>Window</a></code> object before propagating to any of the nodes,
as if the <code><a href=#window>Window</a></code> object was the parent of the
<code><a href=#document>Document</a></code> in the dispatch chain.</li>

<li>In the bubble phase, the event must propagate up to the
<code><a href=#window>Window</a></code> object at the end of the phase, unless bubbling
has been prevented, again as if the <code><a href=#window>Window</a></code> object was
the parent of the <code><a href=#document>Document</a></code> in the dispatch chain.</li>
agent must act as if, for the purposes of <a href=#concept-event-dispatch title=concept-event-dispatch>event dispatching</a>, the
<code><a href=#window>Window</a></code> object is the parent of the
<code><a href=#document>Document</a></code> object. <a href=#refsDOMCORE>[DOMCORE]</a></p>

</ol></div>
</div>


<h3 id=atob><span class=secno>7.2 </span>Base64 utility methods</h3>
Expand Down
33 changes: 10 additions & 23 deletions source
Expand Up @@ -2133,10 +2133,10 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
data.</p>

<p>In the contexts of events, the terms <dfn title="">fire</dfn> and
<dfn title="">dispatch</dfn> are used as defined in the DOM Core
specification: firing an event means to create and dispatch it, and
dispatching an event means to follow the steps that propagate the
event through the tree. The term <dfn
<dfn title="concept-event-dispatch">dispatch</dfn> are used as
defined in the DOM Core specification: firing an event means to
create and dispatch it, and dispatching an event means to follow the
steps that propagate the event through the tree. The term <dfn
title="concept-events-trusted">trusted event</dfn> is used to refer
to events that have the <span>trusted flag</span> set. <a
href="#refsDOMCORE">[DOMCORE]</a></p>
Expand Down Expand Up @@ -41873,9 +41873,7 @@ v6DVT (also check for '- -' bits in the part above) -->
wholesale, with no composition, alpha blending, no shadows,
etc.</p>

<p>If the first argument is null, throws a
<code>TypeMismatchError</code> exception. Throws a
<code>NotSupportedError</code> exception if any of the other
<p>Throws a <code>NotSupportedError</code> exception if any of the
arguments are not finite.</p>

</dd>
Expand Down Expand Up @@ -78882,22 +78880,11 @@ interface <dfn>Function</dfn> {
<p>When an event is dispatched at a DOM node in a
<code>Document</code> in a <span>browsing context</span>, if the
event is not a <code title="event-load">load</code> event, the user
agent must also dispatch the event to the <code>Window</code>, as
follows:</p>

<ol>

<li>In the capture phase, the event must propagate to the
<code>Window</code> object before propagating to any of the nodes,
as if the <code>Window</code> object was the parent of the
<code>Document</code> in the dispatch chain.</li>

<li>In the bubble phase, the event must propagate up to the
<code>Window</code> object at the end of the phase, unless bubbling
has been prevented, again as if the <code>Window</code> object was
the parent of the <code>Document</code> in the dispatch chain.</li>

</ol>
agent must act as if, for the purposes of <span
title="concept-event-dispatch">event dispatching</span>, the
<code>Window</code> object is the parent of the
<code>Document</code> object. <a
href="#refsDOMCORE">[DOMCORE]</a></p>

</div>

Expand Down

0 comments on commit 19da6fb

Please sign in to comment.