Skip to content

Commit

Permalink
[e] (0) Clarify when the drag-and-drop steps run.
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.whatwg.org/webapps@4621 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jan 23, 2010
1 parent fa0014e commit a0afd5c
Show file tree
Hide file tree
Showing 3 changed files with 54 additions and 34 deletions.
29 changes: 18 additions & 11 deletions complete.html
Expand Up @@ -19694,7 +19694,7 @@ <h4 id=the-iframe-element><span class=secno>4.8.3 </span>The <dfn><code>iframe</

<div class=example>

<p class=xxx>example for srcdoc here</p>
<p class=XXX>example for srcdoc here</p>

</div>

Expand Down Expand Up @@ -62089,19 +62089,26 @@ <h4 id=drag-and-drop-processing-model><span class=secno>8.9.4 </span>Drag-and-dr
Initially, it has the value "none". It is updated by the user agent
as described in the steps below.</p>

<p>User agents must, every 350ms (&plusmn;200ms), perform the
following steps in sequence. (If the user agent is still performing
the previous iteration of the sequence when the next iteration
becomes due, the user agent must not execute the overdue iteration,
effectively "skipping missed frames" of the drag-and-drop
operation.)</p>
<p>User agents must, as soon as the drag operation is initiated and
every 350ms (&plusmn;200ms) thereafter for as long as the drag
operation is ongoing, <a href=#queue-a-task>queue a task</a> to perform the
following steps in sequence:</p>

<ol><li>

<p>First, the user agent must fire a <code title=event-drag><a href=#event-drag>drag</a></code> event at the <a href=#source-node>source
node</a>. If this event is canceled, the user agent must set
the <a href=#current-drag-operation>current drag operation</a> to none (no drag
operation).</p>
<p>If the user agent is still performing the previous iteration of
the sequence (if any) when the next iteration becomes due, the
user agent must not execute the overdue iteration, effectively
"skipping missed frames" of the drag-and-drop operation.</p>

</li>

<li>

<p>The user agent must fire a <code title=event-drag><a href=#event-drag>drag</a></code>
event at the <a href=#source-node>source node</a>. If this event is canceled,
the user agent must set the <a href=#current-drag-operation>current drag operation</a> to
none (no drag operation).</p>

</li>

Expand Down
29 changes: 18 additions & 11 deletions index
Expand Up @@ -19594,7 +19594,7 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>

<div class=example>

<p class=xxx>example for srcdoc here</p>
<p class=XXX>example for srcdoc here</p>

</div>

Expand Down Expand Up @@ -61293,19 +61293,26 @@ State: &lt;OUTPUT NAME=I&gt;1&lt;/OUTPUT&gt; &lt;INPUT VALUE="Increment" TYPE=BU
Initially, it has the value "none". It is updated by the user agent
as described in the steps below.</p>

<p>User agents must, every 350ms (&plusmn;200ms), perform the
following steps in sequence. (If the user agent is still performing
the previous iteration of the sequence when the next iteration
becomes due, the user agent must not execute the overdue iteration,
effectively "skipping missed frames" of the drag-and-drop
operation.)</p>
<p>User agents must, as soon as the drag operation is initiated and
every 350ms (&plusmn;200ms) thereafter for as long as the drag
operation is ongoing, <a href=#queue-a-task>queue a task</a> to perform the
following steps in sequence:</p>

<ol><li>

<p>First, the user agent must fire a <code title=event-drag><a href=#event-drag>drag</a></code> event at the <a href=#source-node>source
node</a>. If this event is canceled, the user agent must set
the <a href=#current-drag-operation>current drag operation</a> to none (no drag
operation).</p>
<p>If the user agent is still performing the previous iteration of
the sequence (if any) when the next iteration becomes due, the
user agent must not execute the overdue iteration, effectively
"skipping missed frames" of the drag-and-drop operation.</p>

</li>

<li>

<p>The user agent must fire a <code title=event-drag><a href=#event-drag>drag</a></code>
event at the <a href=#source-node>source node</a>. If this event is canceled,
the user agent must set the <a href=#current-drag-operation>current drag operation</a> to
none (no drag operation).</p>

</li>

Expand Down
30 changes: 18 additions & 12 deletions source
Expand Up @@ -20949,7 +20949,7 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>

<div class="example">

<p class="xxx">example for srcdoc here</p>
<p class="XXX">example for srcdoc here</p>

</div>

Expand Down Expand Up @@ -71486,22 +71486,28 @@ interface <dfn>SQLTransactionSync</dfn> {
Initially, it has the value "none". It is updated by the user agent
as described in the steps below.</p>

<p>User agents must, every 350ms (&#xB1;200ms), perform the
following steps in sequence. (If the user agent is still performing
the previous iteration of the sequence when the next iteration
becomes due, the user agent must not execute the overdue iteration,
effectively "skipping missed frames" of the drag-and-drop
operation.)</p>
<p>User agents must, as soon as the drag operation is initiated and
every 350ms (&#xB1;200ms) thereafter for as long as the drag
operation is ongoing, <span>queue a task</span> to perform the
following steps in sequence:</p>

<ol>

<li>

<p>First, the user agent must fire a <code
title="event-drag">drag</code> event at the <span>source
node</span>. If this event is canceled, the user agent must set
the <span>current drag operation</span> to none (no drag
operation).</p>
<p>If the user agent is still performing the previous iteration of
the sequence (if any) when the next iteration becomes due, the
user agent must not execute the overdue iteration, effectively
"skipping missed frames" of the drag-and-drop operation.</p>

</li>

<li>

<p>The user agent must fire a <code title="event-drag">drag</code>
event at the <span>source node</span>. If this event is canceled,
the user agent must set the <span>current drag operation</span> to
none (no drag operation).</p>

</li>

Expand Down

0 comments on commit a0afd5c

Please sign in to comment.