diff options
| author | jamesr@chromium.org <jamesr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-04-27 01:08:15 +0000 |
|---|---|---|
| committer | jamesr@chromium.org <jamesr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-04-27 01:08:15 +0000 |
| commit | c084330e0809fe289a5c6e307aefc437249192e3 (patch) | |
| tree | b8077dd4028c9bf65d2142db68209cc8aca82ab0 /ipc | |
| parent | dd398db6721ac0a3cd427d966f15fbe9d620b984 (diff) | |
| download | chromium_src-c084330e0809fe289a5c6e307aefc437249192e3.zip chromium_src-c084330e0809fe289a5c6e307aefc437249192e3.tar.gz chromium_src-c084330e0809fe289a5c6e307aefc437249192e3.tar.bz2 | |
Add a new pair of IPC categories for messages that need handling as input events
The compositor thread input filtering mechanism adds the possibility of
handling some IPCs in the render process main thread in a different order than
they were sent from the browser process since it filters some messages from the
IO thread. For the most part, this is OK since the exact order of different
types of messages is not important but there are some input-related messages
that do need to processed in order - for instance MouseCaptureLost
(see crbug.com/231532).
This adds a new IPC class, InputMsg, for messages that need input-like
filtering and InputHostMsg for their ACKs. All messages of this class are
routed through the compositor thread to preserve order.
BUG=233365
Review URL: https://chromiumcodereview.appspot.com/14487003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196907 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ipc')
| -rw-r--r-- | ipc/ipc_message_start.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/ipc/ipc_message_start.h b/ipc/ipc_message_start.h index ab01171..3381021 100644 --- a/ipc/ipc_message_start.h +++ b/ipc/ipc_message_start.h @@ -11,6 +11,7 @@ enum IPCMessageStart { AutomationMsgStart = 0, ViewMsgStart, + InputMsgStart, PluginMsgStart, ProfileImportMsgStart, TestMsgStart, |