diff options
| author | sadrul <sadrul@chromium.org> | 2015-12-07 14:57:03 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-12-07 22:58:40 +0000 |
| commit | 07a19a2bc8560ce5e99cd27a9830089683153046 (patch) | |
| tree | e8f3fc28e168dd60258f2f86b3e9df0ad952ac6c /components/mus/public/cpp/tests/window_server_test_base.h | |
| parent | 294d703324a8914ca636209b32fca94034ce9e16 (diff) | |
| download | chromium_src-07a19a2bc8560ce5e99cd27a9830089683153046.zip chromium_src-07a19a2bc8560ce5e99cd27a9830089683153046.tar.gz chromium_src-07a19a2bc8560ce5e99cd27a9830089683153046.tar.bz2 | |
mus: Allow a mus app to manually/explicitly ack an event.
Instead of dispatching an input event to all mus::WindowObservers of a
mus::Window, have an explicit mus::InputEventHandler, which is responsible
for processing events for a Window. The InputEventHandler receives the
target, the event, and the ack callback. If it wants to explicitly ack the
event (possibly asynchronously, e.g. chrome renderer, when it receives the
event in the compositor thread, but wants to process the event in the main
thread before ack'ing), it can take the ack callback, and return true to
notify the client-lib.
BUG=none
Review URL: https://codereview.chromium.org/1492963003
Cr-Commit-Position: refs/heads/master@{#363617}
Diffstat (limited to 'components/mus/public/cpp/tests/window_server_test_base.h')
0 files changed, 0 insertions, 0 deletions