diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-02 18:43:01 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-02 18:43:01 +0000 |
| commit | cf06a4ae0a4313622ffcecc6a3520405128d230d (patch) | |
| tree | 285b3160e6bea58f55390eef874fd6e2b109ea8e /ipc/param_traits_write_macros.h | |
| parent | d0aff40acbcf6714daef11e343f409bb11ea7678 (diff) | |
| download | chromium_src-cf06a4ae0a4313622ffcecc6a3520405128d230d.zip chromium_src-cf06a4ae0a4313622ffcecc6a3520405128d230d.tar.gz chromium_src-cf06a4ae0a4313622ffcecc6a3520405128d230d.tar.bz2 | |
Inform the browser about mouse input in windowed plugins to ensure that we expect actions
which correspond to user gesture like downloads, external protocol launches, etc. Actions
occurring in the context of user input need to be allowed. To achieve this we send over
the WM_PARENTNOTIFY message to the RVH window which turns on user gesture. As per msdn
this message should be received automatically which does not appear to be the case.
All this means that we trust the plugin. However this does not add a new attack vector
as the plugin can send messages to other windows in the desktop anyway.
Fixes bug http://code.google.com/p/chromium/issues/detail?id=41157
BUG=41157
TEST=As described in the bug.
Review URL: http://codereview.chromium.org/6592092
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76566 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ipc/param_traits_write_macros.h')
0 files changed, 0 insertions, 0 deletions