- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 23 Jan 2010 10:29:42 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv10019 Modified Files: Overview.html Log Message: Clarify when the drag-and-drop steps run. (whatwg r4621) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3681 retrieving revision 1.3682 diff -u -d -r1.3681 -r1.3682 --- Overview.html 23 Jan 2010 00:14:25 -0000 1.3681 +++ Overview.html 23 Jan 2010 10:29:39 -0000 1.3682 @@ -16870,7 +16870,7 @@ <code><a href="#windowproxy">WindowProxy</a></code> object will proxy new <code><a href="#window">Window</a></code> objects for new <code>Document</code> objects, but the <code title="attr-iframe-src"><a href="#attr-iframe-src">src</a></code> attribute will not change.<div class="example"> - <p class="xxx">example for srcdoc here</p> + <p class="XXX">example for srcdoc here</p> </div><hr><p>The <dfn id="attr-iframe-name" title="attr-iframe-name"><code>name</code></dfn> attribute, if present, must be a <a href="#valid-browsing-context-name">valid browsing context @@ -48184,19 +48184,26 @@ 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>
Received on Saturday, 23 January 2010 10:29:43 UTC