Re: [whatwg] Exposing filenames in DataTransfer

2010-10-29 Thread Daniel Cheng
In that case, I'd like to propose a set of MIME types that the spec explicitly mentions for interoperability with native apps: - text/plain for compatibility with IE - text/uri-list for compatibility with IE - text/html for rich text formatting. One potential usage--a reference site such as

Re: [whatwg] Exposing filenames in DataTransfer

2010-10-26 Thread Anne van Kesteren
On Thu, 21 Oct 2010 02:20:57 +0200, Daniel Cheng dch...@chromium.org wrote: To clarify, I wasn't proposing that pages need to know details of a particular OS. Things like text/plain, text/uri-list, text/html, etc. are automatically mapped by the UA to whatever the appropriate platform

Re: [whatwg] Exposing filenames in DataTransfer

2010-10-20 Thread Daniel Cheng
To clarify, I wasn't proposing that pages need to know details of a particular OS. Things like text/plain, text/uri-list, text/html, etc. are automatically mapped by the UA to whatever the appropriate platform idiom is. I just thought it would be useful to also expose things that the UA itself

Re: [whatwg] Exposing filenames in DataTransfer

2010-10-19 Thread Anne van Kesteren
On Tue, 19 Oct 2010 00:15:27 +0200, Daniel Cheng dch...@chromium.org wrote: Sorry, I'm using properties as a generic term for different types of data that might be set in a drag. A lot of file managers try to be helpful and populate alternative metadata for a file. Some of this metadata

[whatwg] Exposing filenames in DataTransfer

2010-10-18 Thread Daniel Cheng
I've been working on better support of arbitrary MIME types in WebKit for some time, and I had some implementation questions. In the past, UAs seem to have gone out of their way to make sure full filesystem paths aren't exposed to the Javascript (e.g. in the file input control). When I did the

Re: [whatwg] Exposing filenames in DataTransfer

2010-10-18 Thread Tab Atkins Jr.
On Mon, Oct 18, 2010 at 1:59 PM, Daniel Cheng dch...@chromium.org wrote: However, this leads to issues like file system paths being exposed through properties like x-special/gnome-icon-list or even text/plain. What is the expected behavior here? Mirroring the native dragging clipboard allows

Re: [whatwg] Exposing filenames in DataTransfer

2010-10-18 Thread Daniel Cheng
Sorry, I'm using properties as a generic term for different types of data that might be set in a drag. A lot of file managers try to be helpful and populate alternative metadata for a file. Some of this metadata contains file system paths. If the web dragging clipboard mirrors the native dragging

Re: [whatwg] Exposing filenames in DataTransfer

2010-10-18 Thread Robert O'Callahan
On Tue, Oct 19, 2010 at 9:59 AM, Daniel Cheng dch...@chromium.org wrote: However, this leads to issues like file system paths being exposed through properties like x-special/gnome-icon-list or even text/plain. What is the expected behavior here? Mirroring the native dragging clipboard allows