Fix the handling of user gestures for external protocol handler dialogs.

chrome/browser/autocomplete/autocomplete_input.cc

Index: chrome/browser/autocomplete/autocomplete_input.cc
diff --git a/chrome/browser/autocomplete/autocomplete_input.cc b/chrome/browser/autocomplete/autocomplete_input.cc
index ea4285172a6a3c21fd963991f877554d079d22ff..770fe09f5ff925551fe4ea8582427d225c1c6a43 100644
--- a/chrome/browser/autocomplete/autocomplete_input.cc
+++ b/chrome/browser/autocomplete/autocomplete_input.cc
@@ -198,6 +198,9 @@ AutocompleteInput::Type AutocompleteInput::Parse(
     // handlable schemes (e.g. "javascript") may be treated as "blocked" by the
     // external protocol handler because we don't want pages to open them, but
     // users still can.
+    // External protocol handler checks for the existence of a user gesture.
+    // Fake one so that we don't always get a BLOCK result.

[Peter Kasting, 2014/03/28 22:56:37]

Nit: How about this comment, appended at the end of the previous paragraph:

Note that the protocol handler needs to be informed that omnibox input should
always be considered "user gesture-triggered", lest it always return BLOCK.

[meacer, 2014/03/28 23:13:57]

Done.

+    ExternalProtocolHandler::ScopedUserGesture skip_user_gesture_check;
     ExternalProtocolHandler::BlockState block_state =
         ExternalProtocolHandler::GetBlockState(
             base::UTF16ToUTF8(parsed_scheme));