On 1/31/12 11:40 PM, Ryosuke Niwa wrote:
On Tue, Jan 31, 2012 at 11:11 PM, Charles Pritchard <ch...@jumis.com
<mailto:ch...@jumis.com>> wrote:
On 1/31/12 10:55 PM, Ryosuke Niwa wrote:
I think I understand what you're saying now. For your use
case, you should
use dropzone content attribute:
http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#the-dropzone-attribute
Then all you have to write is a drop event handler where you
have access to
clipboard data.
Well that certainly justifies the dropzone attribute. Have any
vendors implemented it?
We implement webkitdropzone.
The webkitdropzone semantic seems absolutely correct for text entry
fields such as input text, contentEditable and textarea.
But, the implementation in Chrome does not move the caret, and I don't
see an easy way to convey "accept all files".
WebKit was recently updated to match the specs:
https://bugs.webkit.org/show_bug.cgi?id=74834
The semantics in Chrome M16 were "copy f:image/jpeg" instead of "copy
file:image/jpeg".
What's the proper way to convey wildcards? "copy file:*/*" ?
The behavior of dropzone in M16 has the same behavior as stopPropagation
ondragover when the mime type matches.
When the mime type does not match, it has the desired behavior of moving
the caret. I'd imagine this is a bug, not intentional.
-Charles
