hixie: Make </rt> optional in WebSRT. Add some ideas for the drag-and-drop model. (whatwg r5574)

hixie: Make </rt> optional in WebSRT. Add some ideas for the drag-and-
drop model. (whatwg r5574)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4455&r2=1.4456&f=h
http://html5.org/tools/web-apps-tracker?from=5573&to=5574

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4455
retrieving revision 1.4456
diff -u -d -r1.4455 -r1.4456
--- Overview.html 1 Oct 2010 18:56:37 -0000 1.4455
+++ Overview.html 4 Oct 2010 21:23:57 -0000 1.4456
@@ -316,7 +316,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-1-october-2010">Editor's Draft 1 October 2010</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-4-october-2010">Editor's Draft 4 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>
@@ -422,7 +422,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 1 October 2010 Editor's Draft.
+  This specification is the 4 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
@@ -50779,6 +50779,7 @@
      * We should let drop targets communicate back to drag sources if
        they want to communicate. (e.g. expose Window, and thus
        postMessage(), on the dataTransfer object on drop.)
+       Or maybe just use a MessagePort!
 
        We should let drag sources provide a set of options via a
        context menu when the drop happens. (So that, e.g., the source
@@ -50808,13 +50809,18 @@
                           .add(blobData)
                           .add(fileData)
                           .add(dataTransferItem)
+                          .add(promise)
                           .clear()
 
          DataTransferItem.kind = 'string', 'file', 'blob', ...
                          .type = MIME type
-                         .binary = boolean
+                         .binaryOnly
                          .getTextData(function callback (data)) - throws if binary is true
-                         .getBlob() - returns File or Blob
+                         .getBlob() - returns File or Blob (which are async anyway)
+
+         DataTransferPromise.type = 'string' or 'file' or 'blob'
+                            .onneeddata - can wait until this fires to provide data
+                            .setData() - call this once you have data, must be the right type
 
 --><p>This section defines an event-based drag-and-drop mechanism.<p>This specification does not define exactly what a
   <em>drag-and-drop operation</em> actually is.<p>On a visual medium with a pointing device, a drag operation could

Received on Monday, 4 October 2010 21:24:52 UTC