[prev in list] [next in list] [prev in thread] [next in thread]
List: html5-commit-watchers
Subject: [html5] r4621 - [e] (0) Clarify when the drag-and-drop steps run.
From: whatwg () whatwg ! org
Date: 2010-01-23 10:29:35
Message-ID: 20100123102935.A098E80580DB () ps20323 ! dreamhostps ! com
[Download RAW message or body]
Author: ianh
Date: 2010-01-23 02:29:33 -0800 (Sat, 23 Jan 2010)
New Revision: 4621
Modified:
complete.html
index
source
Log:
[e] (0) Clarify when the drag-and-drop steps run.
Modified: complete.html
===================================================================
--- complete.html 2010-01-23 00:14:19 UTC (rev 4620)
+++ complete.html 2010-01-23 10:29:33 UTC (rev 4621)
@@ -19694,7 +19694,7 @@
<div class=example>
- <p class=xxx>example for srcdoc here</p>
+ <p class=XXX>example for srcdoc here</p>
</div>
@@ -62089,24 +62089,31 @@
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 (±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 (±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>
+
+ <li>
+
<p>Next, if the <code title=event-drag><a href=#event-drag>drag</a></code> event \
was not canceled and the user has not ended the drag-and-drop operation,
the user agent must check the state of the drag-and-drop
Modified: index
===================================================================
--- index 2010-01-23 00:14:19 UTC (rev 4620)
+++ index 2010-01-23 10:29:33 UTC (rev 4621)
@@ -19594,7 +19594,7 @@
<div class=example>
- <p class=xxx>example for srcdoc here</p>
+ <p class=XXX>example for srcdoc here</p>
</div>
@@ -61293,24 +61293,31 @@
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 (±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 (±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>
+
+ <li>
+
<p>Next, if the <code title=event-drag><a href=#event-drag>drag</a></code> event \
was not canceled and the user has not ended the drag-and-drop operation,
the user agent must check the state of the drag-and-drop
Modified: source
===================================================================
--- source 2010-01-23 00:14:19 UTC (rev 4620)
+++ source 2010-01-23 10:29:33 UTC (rev 4621)
@@ -20949,7 +20949,7 @@
<div class="example">
- <p class="xxx">example for srcdoc here</p>
+ <p class="XXX">example for srcdoc here</p>
</div>
@@ -71486,27 +71486,33 @@
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 (±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 (±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>
+
+ <li>
+
<p>Next, if the <code title="event-drag">drag</code> event was not
canceled and the user has not ended the drag-and-drop operation,
the user agent must check the state of the drag-and-drop
_______________________________________________
Commit-Watchers mailing list
Commit-Watchers@lists.whatwg.org
http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic