summaryrefslogtreecommitdiffstats
path: root/chrome/chrome_browser.gypi
diff options
context:
space:
mode:
authordcheng@chromium.org <dcheng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-04-06 16:58:34 +0000
committerdcheng@chromium.org <dcheng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-04-06 16:58:34 +0000
commit13a1166eb46a5b98e1cf5fce21ae327f3e059aa5 (patch)
tree54c23ec7909d15610a87866ea27e1a9be7ffa9da /chrome/chrome_browser.gypi
parenta3f99af364ffec8c47948fb0f5eeacf97e77908b (diff)
downloadchromium_src-13a1166eb46a5b98e1cf5fce21ae327f3e059aa5.zip
chromium_src-13a1166eb46a5b98e1cf5fce21ae327f3e059aa5.tar.gz
chromium_src-13a1166eb46a5b98e1cf5fce21ae327f3e059aa5.tar.bz2
Win32 plumbing for dragend event.
This plumbs the actual dropEffect that occurred back into WebKit so that dragend is dispatched with the correct dropEffect. Note that this only helps with drags that start in Chrome and end outside of Chrome. Since WebDropTarget always lies and claims that no drop occurred, drags that start in Chrome and end in Chrome will still be incorrect. BUG=39399 TEST=Manual testing using the attached test case on the bug. Review URL: http://codereview.chromium.org/1136007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@43726 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_browser.gypi')
-rw-r--r--chrome/chrome_browser.gypi2
1 files changed, 2 insertions, 0 deletions
diff --git a/chrome/chrome_browser.gypi b/chrome/chrome_browser.gypi
index 4a0502a..31a0109 100644
--- a/chrome/chrome_browser.gypi
+++ b/chrome/chrome_browser.gypi
@@ -2057,6 +2057,8 @@
'browser/tab_contents/web_drag_source_win.h',
'browser/tab_contents/web_drag_dest_gtk.cc',
'browser/tab_contents/web_drag_dest_gtk.h',
+ 'browser/tab_contents/web_drag_utils_win.cc',
+ 'browser/tab_contents/web_drag_utils_win.h',
'browser/tab_contents/web_drop_target_win.cc',
'browser/tab_contents/web_drop_target_win.h',
'browser/tab_menu_model.cc',