diff options
| author | satorux@chromium.org <satorux@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-05-09 07:07:54 +0000 |
|---|---|---|
| committer | satorux@chromium.org <satorux@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-05-09 07:07:54 +0000 |
| commit | ad688f24f2931740f5c570b1ed89ae628950a857 (patch) | |
| tree | 0e82a57225d135b72c4051b5f57b46c07a0b070d /tools | |
| parent | 294987d4e9a4c6bcd748d2b30ee8a8f39fa179a6 (diff) | |
| download | chromium_src-ad688f24f2931740f5c570b1ed89ae628950a857.zip chromium_src-ad688f24f2931740f5c570b1ed89ae628950a857.tar.gz chromium_src-ad688f24f2931740f5c570b1ed89ae628950a857.tar.bz2 | |
Add plumbing for file display names for drag and drop
On HTML5 file system, the real path names are human-unreadable
hence we should propagate human-readable display names when
performing drag-and-drop.
WebKit patch was in http://trac.webkit.org/changeset/116186
FWIW, I originally added display_names to WebDropData but the resulting
code was not desirable:
- checking if the size of |display_names| match with |file_names|
is not clean (parallel arrays like these are not good in general)
- adding GetDisplayNames/SetDisplayNames() to every Provider
implementation looked more complicated than changing the existing
GetFilenames/SetFilenames() to take a struct.
BUG=chromium-os:30419,chromium-os:30665
TEST=confirm that the correct file name is shown by the steps described in crosbug.co/30665
Review URL: https://chromiumcodereview.appspot.com/10382056
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136000 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions