| commit | 030a0491b1d2e0bda3933e0d1f4a6a90c0b06853 | |
| author | sadrul@chromium.org <sadrul@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Sat, 5 Apr 2014 17:38:01 +0000 (5 17:38 +0000) | ||
| committer | sadrul@chromium.org <sadrul@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Sat, 5 Apr 2014 17:38:01 +0000 (5 17:38 +0000) | ||
| tree | a5bbf4294fd75a1978092bdd0c03e6e374b4f6da | treesnapshot (tar.gz zip) |
| parent | f65e97e447b789af3a8dc653d8801e8c6f24f935 | commitdiff |
base: Do not allow MessagePumpObservers to consume events.
There is currently a single message-pump observer that can consume an event,
and it does so only when the num-lock key is pressed on Chrome OS. But it
doesn't need to consume the event, because no other dispatcher/observer cares
about this event. So remove a MessagePumpObserver's ability to consume an
event. This makes the code cleaner, and easier to understand.
BUG=354062
R=darin@chromium.org, derat@chromium.org, sky@chromium.org
Review URL: https://codereview.chromium.org/223483002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@262019 0039d316-1c4b-4281-b951-d872f2087c98
There is currently a single message-pump observer that can consume an event,
and it does so only when the num-lock key is pressed on Chrome OS. But it
doesn't need to consume the event, because no other dispatcher/observer cares
about this event. So remove a MessagePumpObserver's ability to consume an
event. This makes the code cleaner, and easier to understand.
BUG=354062
R=darin@chromium.org, derat@chromium.org, sky@chromium.org
Review URL: https://codereview.chromium.org/223483002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@262019 0039d316-1c4b-4281-b951-d872f2087c98
25 files changed: