- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Tue, 14 Oct 2014 13:07:54 +0000
- To: Device APIs Working Group <public-device-apis@w3.org>
- CC: Emmanuel Toledo <emmanuel.toledo@assertus.com>
Hi All, On 13 Oct 2014, at 16:36, Emmanuel Toledo <emmanuel.toledo@assertus.com> wrote: > You are right :), I appreciate your help , thanks for your time. [...] >> This could help on the issue when a device has file synchronization >> with a cloud service(i.e. ICloud, Google drive, One drive, etc.) and the developer does not want to make the user's capture image shareable and potentially making that image public. In example on Windows Phone the captured image gets saved on the device, there could be more devices with this potential problem. > > Wouldn't this problem be addressed by simply requiring that a conformant implementation must not save the captured media anywhere? Given this addresses Emmanuel’s concern, I added the following to the spec: [[ When the capture attribute is specified, the user agent MUST NOT save the captured media to any data storage, local or remote. NOTE When scripts gain access to the files selected from the file picker (represented by a FileList object), they can use various mechanisms to store the captured media. These mechanisms are out of scope for this specification. ]] See the ED [1] and diff [2]. A note regarding testability: this assertion must be manually tested. All - please let me know if you have concerns with the suggested change. Thanks, -Anssi [1] http://dev.w3.org/2009/dap/camera/ [2] http://dev.w3.org/cvsweb/2009/dap/camera/Overview.src.html.diff?r1=1.13;r2=1.14;f=h
Received on Tuesday, 14 October 2014 13:09:25 UTC