- From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 16 Jul 2010 13:48:29 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/camera
In directory hutz:/tmp/cvs-serv10227
Modified Files:
Overview.html
Log Message:
pushing WebIDL interfaces after HTML form integration
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/camera/Overview.html,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -d -r1.95 -r1.96
--- Overview.html 16 Jul 2010 13:45:17 -0000 1.95
+++ Overview.html 16 Jul 2010 13:48:27 -0000 1.96
@@ -77,8 +77,57 @@
</section>
+
+ <section id="formaccess">
+ <h2>Capture aware file-select control</h2>
+
+ <p>This section is normative.</p>
+
+ <p class="note">[[!HTML5]] <a href="http://dev.w3.org/html5/spec/number-state.html#file-upload-state">links <code><input type="file"></code></a> to the File interface. This specification defines a refined <code>MediaFile</code> interface to be used when the <code>accept</code> attribute take certain values — this will require coordination with the HTML5 Working Group.</p>
+
+ <p>If input element in the File Upload state [[!HTML5]] contains
+ accept attribute with values <code>image/*</code>,
+ <code>sound/*</code>, or <code>video/*</code>, the user agent can
+ invoke a file picker that allows respectively the user to take a
+ picture, record a sound file, or record a video in addition to
+ selecting an existing file from the file system.</p>
+
+ <p>See the <a href="#uiexamples">User Interface Examples</a> appendix for the illustration.
+
+ <p>In case the user chooses to capture video, audio, or image
+ content, the user agent creates media files on the fly <a href="http://dev.w3.org/html5/spec/number-state.html#file-upload-state">as
+ specified</a> in [[HTML5]].</p>
+
+ <p>If the user captures media files successfully, the
+ <code>files</code> attribute [[HTML5]] MUST return a <a
+ href="#medialist">MediaList</a> object that represents the
+ current captured content instead of <code>FileList</code>
+ [[!FILE-API]] object as specified in [[!HTML5]].
+
+ <pre class="example sh_javascript_dom"><input type="file" accept="image/*"> </pre>
+</section>
+
+ <section id="formaccess">
+ <h2>The <code>capture</code> parameter</h2>
+
+ <p>This section is normative.</p>
+
+
+ <p>The <code>capture</code> parameter may be specified on the media type values of the <code>accept</code> attribute to provide user agents with a hint of that by the default a file picker should be in media capturing mode.</p>
+
+ <p class="note">[[!HTML5]] <a href="http://dev.w3.org/html5/spec/number-state.html#attr-input-accept">defines the <code>accept</code> attribute to take no parameters on MIME types</a>. This specification proposes to use a MIME type parameter — this will require coordination with the HTML5 Working Group.</p>
+
+
+ <p>The <code>capture</code> parameter can take one of the following values: <code>camera</code>, <code>camcorder</code>, <code>microphone</code>, <code>filesystem</code>. These values indicate which source the file picker interface should preferably present to the user by default.</p>
+ <p class="note">The values and their exact meaning are still very much in flux.</p>
+
+ <p>For example, the following code indicates that the user is expected to upload an image from the device camera:</p>
+ <pre class="example sh_javascript_dom"><input type="file" accept="image/*;capture=camera"> </pre>
+ <p>A possible rendering of a file picker taking this parameter into account is offered in the <a href="#uiexamples">User Interface Examples appendix</a>.</p>
+</section>
+
<section id="api">
- <h2>API Description</h2>
+ <h2>WebIDL interfaces</h2>
<section id="mediafile"><h3><a>MediaFile</a> interface</h3>
@@ -147,54 +196,6 @@
<dl title="typedef sequence<MediaFile> MediaList" class="idl"></dl>
</section>
- <section id="formaccess">
- <h2>Capture aware file-select control</h2>
-
- <p>This section is normative.</p>
-
- <p class="note">[[!HTML5]] <a href="http://dev.w3.org/html5/spec/number-state.html#file-upload-state">links <code><input type="file"></code></a> to the File interface. This specification defines a refined MediaFile interface to be used when the <code>accept</code> attribute take certain values — this will require coordination with the HTML5 Working Group.</p>
-
- <p>If input element in the File Upload state [[!HTML5]] contains
- accept attribute with values <code>image/*</code>,
- <code>sound/*</code>, or <code>video/*</code>, the user agent can
- invoke a file picker that allows respectively the user to take a
- picture, record a sound file, or record a video in addition to
- selecting an existing file from the file system.</p>
-
- <p>See the <a href="#uiexamples">User Interface Examples</a> appendix for the illustration.
-
- <p>In case the user chooses to capture video, audio, or image
- content, the user agent creates media files on the fly <a href="http://dev.w3.org/html5/spec/number-state.html#file-upload-state">as
- specified</a> in [[HTML5]].</p>
-
- <p>If the user captures media files successfully, the
- <code>files</code> attribute [[HTML5]] MUST return a <a
- href="#medialist">MediaList</a> object that represents the
- current captured content instead of <code>FileList</code>
- [[!FILE-API]] object as specified in [[!HTML5]].
-
- <pre class="example sh_javascript_dom"><input type="file" accept="image/*"> </pre>
-
-
-</section>
-
- <section id="formaccess">
- <h2>The <code>Capture</code> parameter</h2>
-
- <p>This section is normative.</p>
-
-
- <p>The <code>capture</code> parameter may be specified on the media type values of the <code>accept</code> attribute to provide user agents with a hint of that by the default a file picker should be in media capturing mode.</p>
-
- <p class="note">[[!HTML5]] <a href="http://dev.w3.org/html5/spec/number-state.html#attr-input-accept">defines the <code>accept</code> attribute to take no parameters on MIME types</a>. This specification proposes to use a MIME type parameter — this will require coordination with the HTML5 Working Group.</p>
-
-
- <p>The <code>capture</code> parameter can take one of the following values: <code>camera</code>, <code>camcorder</code>, <code>microphone</code>, <code>filesystem</code>. These values indicate which source the file picker interface should preferably present to the user by default.</p>
- <p class="note">The values and their exact meaning are still very much in flux.</p>
-
- <p>For example, the following code indicates that the user is expected to upload an image from the device camera:</p>
- <pre class="example sh_javascript_dom"><input type="file" accept="image/*;capture=camera"> </pre>
-</section>
<section class='appendix' id="uiexamples">
<h2>User Interface Examples</h2>
Received on Friday, 16 July 2010 13:48:31 UTC