events: Remove ability to terminate a nested message-loop from the event-source.

events: Remove ability to terminate a nested message-loop from the event-source.

Terminating a message-loop directly using MessageLoop::QuitNow() can terminate
the message-loop at the incorrect depth. So remove the ability of the event-source
to terminate the message-loop, and require the relevant code that initiated the
nested message-loop to be responsible for terminating it.

BUG=372208
R=sky@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=270483

[sadrul, 2014-05-14 17:46:33]

https://codereview.chromium.org/274383002/diff/40001/ash/accelerators/acceler...
File ash/accelerators/accelerator_dispatcher_linux.cc (right):

https://codereview.chromium.org/274383002/diff/40001/ash/accelerators/acceler...
ash/accelerators/accelerator_dispatcher_linux.cc:72: return
ui::POST_DISPATCH_NONE;
MenuClosedForPossibleAccelerator() (line 66) calls MenuController::CancelAll(),
which in turn calls MenuController::SetExitType(), which should terminate the
nested message-loop when appropriate. So it should not be necessary for the
event-source to terminate it again.

[sky, 2014-05-14 19:09:39]

LGTM

[sadrul, 2014-05-14 21:59:38]

Committed patchset #3 manually as r270483 (presubmit successful).