diff options
author | stuartmorgan@chromium.org <stuartmorgan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-01-12 16:39:03 +0000 |
---|---|---|
committer | stuartmorgan@chromium.org <stuartmorgan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-01-12 16:39:03 +0000 |
commit | a956916ffd429577a979efa34af889801b8ed44e (patch) | |
tree | 8a1e0fb5f875110abaa08606969e610d3c207a09 /chrome | |
parent | 78f7decedbe5e08df8aff92dd46a43f4f6afbc17 (diff) | |
download | chromium_src-a956916ffd429577a979efa34af889801b8ed44e.zip chromium_src-a956916ffd429577a979efa34af889801b8ed44e.tar.gz chromium_src-a956916ffd429577a979efa34af889801b8ed44e.tar.bz2 |
Simplify Mac plugin HandleInputEvent logic
- Consolidates most of the Carbon-only code into a single block, to cut down on ifdef's, and puts it into a runtime conditional so we don't do needless work in Cocoa event plugins.
- Changes the internal logic to be WebInputEvent-based, rather than NPEvent-based
- Updates the stored mouse location on all mouse events (whenever the window moves) since the two are closely related. This means that we will update on mouse-exit, so the location sent to Carbon plugins for null events after the mouse leaves will be just outside the plugin bounds, rather than inside.
BUG=none
TEST=Mouse events should continue to work in both Flash 10.0 and 10.1. Hover effects in Flash 10.0 content should not persist after the mouse is moved out of the plugin.
Review URL: http://codereview.chromium.org/550009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36014 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome')
0 files changed, 0 insertions, 0 deletions