[whatwg] contentEditable and drag and drop cancel
dcheng at chromium.org
Wed Feb 1 16:44:07 PST 2012
The spec doesn't support wildcards today.
On Wed, Feb 1, 2012 at 00:17, Ryosuke Niwa <rniwa at webkit.org> wrote:
> On Wed, Feb 1, 2012 at 12:07 AM, Charles Pritchard <chuck at jumis.com>wrote:
>> 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:
>> The semantics in Chrome M16 were "copy f:image/jpeg" instead of "copy
>> 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.
> In general, our drag & drop support isn't well tested especially inside
> content editable region. I just fixed one of bugs:
> If you see any weird behavior, please file bugs on bugs.webkit.org. We're
> more than happy to fix those bugs (as long as our time and priority of
> things permits).
> - Ryosuke
More information about the whatwg