Disable input events when a JS dialog is showing.

Prior to this patch, you could still send input events and they
would get queued in the renderer to be handled after the JS
dialog was dismissed.  This makes our behavior more like other
browsers.

This also works around a linux/mac bug where the hung renderer dialog would appear when an alert is showing.

BUG=12176

Review URL: http://codereview.chromium.org/160494


git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22415 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 11 insertions, 0 deletions

diff --git a/chrome/browser/renderer_host/render_process_host.h b/chrome/browser/renderer_host/render_process_host.h
index c091e85..ec5d198 100644
--- a/chrome/browser/renderer_host/render_process_host.h
+++ b/chrome/browser/renderer_host/render_process_host.h
@@ -100,6 +100,13 @@ class RenderProcessHost : public IPC::Channel::Sender,
   // initialize a new renderer in place of the current one.
   void UpdateMaxPageID(int32 page_id);
 
+  void set_ignore_input_events(bool ignore_input_events) {
+    ignore_input_events_ = ignore_input_events;
+  }
+  bool ignore_input_events() {
+    return ignore_input_events_;
+  }
+
   // Virtual interface ---------------------------------------------------------
 
   // Initialize the new renderer process, returning true on success. This must
@@ -242,6 +249,10 @@ class RenderProcessHost : public IPC::Channel::Sender,
   // doesn't.
   bool sudden_termination_allowed_;
 
+  // Set to true if we shouldn't send input events.  We actually do the
+  // filtering for this at the render widget level.
+  bool ignore_input_events_;
+
   // See getter above.
   static bool run_renderer_in_process_;