- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 25 Oct 2010 22:32:25 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv4067
Modified Files:
Overview.html
Log Message:
dropzone 1/5: the new model (whatwg r5646)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4523
retrieving revision 1.4524
diff -u -d -r1.4523 -r1.4524
--- Overview.html 23 Oct 2010 00:36:29 -0000 1.4523
+++ Overview.html 25 Oct 2010 22:32:21 -0000 1.4524
@@ -321,7 +321,7 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="editor-s-draft-23-october-2010">Editor's Draft 23 October 2010</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-25-october-2010">Editor's Draft 25 October 2010</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -451,7 +451,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 23 October 2010 Editor's Draft.
+ This specification is the 25 October 2010 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -50158,31 +50158,80 @@
void <a href="#dom-datatransfer-setdragimage" title="dom-DataTransfer-setDragImage">setDragImage</a>(in Element image, in long x, in long y);
void <a href="#dom-datatransfer-addelement" title="dom-DataTransfer-addElement">addElement</a>(in Element element);
-};</pre><p><code><a href="#datatransfer">DataTransfer</a></code> objects can hold pieces of data, each
- associated with a unique format. Formats are generally given by
- <a href="#mime-type" title="MIME type">MIME types</a>, with some values
- special-cased for legacy reasons. However, the API does not enforce
- this; non-MIME-type values can be added as well. All formats are
- identified by strings that are <a href="#converted-to-ascii-lowercase">converted to ASCII
- lowercase</a> by the API.</p><!--
+};</pre><p><code><a href="#datatransfer">DataTransfer</a></code> objects are used to expose the data
+ that underlies a drag-and-drop operation.<p>The data that underlies a drag-and-drop operation, known as the
+ <dfn id="drag-data-store">drag data store</dfn>, consists of an unordered list of items
+ representing the dragged data, and some information used to generate
+ the UI feedback during the drag.<p>Each item representing dragged data in a <a href="#drag-data-store">drag data
+ store</a> has the following information:<ul><li>
-XXX
+ <p>The type or format of the data, generally given by a <a href="#mime-type">MIME
+ type</a>. Some values that are not <a href="#mime-type" title="MIME type">MIME
+ types</a> are special-cased for legacy reasons. The API does
+ not enforce the use of <a href="#mime-type" title="MIME type">MIME types</a>;
+ other values can be used as well. In all cases, however, the
+ values are all <a href="#converted-to-ascii-lowercase">converted to ASCII lowercase</a> by the
+ API.</p>
-here we say what the DataTransfer objects model is, and that it can be in a read/write mode, secret mode, read-only mode
+ </li>
-model is:
- - list of items (see DataTransferItem above)
- - the drag image (search for "drag feedback"):
- - elements
- - bitmap, x, y
+ <li>
-plan:
- 1. describe model
- 2. replace the existing API definitions with links to this model
- 3. expose model with new API
- 4. add dropzone="..." feature
+ <p>The kind of data:</p>
---><dl class="domintro"><dt><var title="">dataTransfer</var> . <code title="dom-DataTransfer-dropEffect"><a href="#dom-datatransfer-dropeffect">dropEffect</a></code> [ = <var title="">value</var> ]</dt>
+ <dl><dt>Plain Unicode string</dt>
+ <dd>
+ <p>Raw text.</p>
+ </dd>
+
+ <dt>Blob</dt>
+ <dd>
+ <p>Binary data.</p>
+ </dd>
+
+ <dt>File</dt>
+ <dd>
+ <p>Binary data with a file name.</p>
+ </dd>
+
+ </dl></li>
+
+ </ul><p>The information in a <a href="#drag-data-store">drag data store</a> used to
+ generate the UI feedback during the drag consists of:<ul><li>A list of zero or more elements.</li>
+
+ <li>Optionally, a bitmap image and the coordinate of a point within
+ that image.</li>
+
+ </ul><p>A <a href="#drag-data-store">drag data store</a> is created at the start of a
+ drag-and-drop operation in the <i>read/write mode</i>, and then
+ progresses through the following three modes as the operation
+ proceeds:<dl><dt>Read/write mode</dt>
+ <dd>
+
+ <p>At the start of the drag. New data can be added to the
+ <a href="#drag-data-store">drag data store</a>.</p>
+
+ </dd>
+
+ <dt>Protected mode</dt>
+ <dd>
+
+ <p>During the drag. The formats and kinds in the <a href="#drag-data-store">drag data
+ store</a> list of items representing dragged data can be
+ enumerated, but the data itself is unavailable and no new data can
+ be added.</p>
+
+ </dd>
+
+ <dt>Read-only mode</dt>
+ <dd>
+
+ <p>After the drop. The list of items representing dragged data can
+ be read, including the data. No new data can be added.</p>
+
+ </dd>
+
+ </dl><dl class="domintro"><dt><var title="">dataTransfer</var> . <code title="dom-DataTransfer-dropEffect"><a href="#dom-datatransfer-dropeffect">dropEffect</a></code> [ = <var title="">value</var> ]</dt>
<dd>
@@ -50269,7 +50318,17 @@
</dd>
- </dl><div class="impl">
+ </dl><!--
+
+XXX
+
+plan:
+ 2. replace the existing API definitions with links to this model
+ 3. make it clear there's a new DataTransfer object with each event
+ 4. expose model with new API
+ 5. add dropzone="..." feature
+
+--><div class="impl">
<p>When a <code><a href="#datatransfer">DataTransfer</a></code> object is created, it must be
initialized as follows:</p>
Received on Monday, 25 October 2010 22:32:26 UTC