Commit 4ecf951f authored by mihaip@chromium.org's avatar mihaip@chromium.org

Don't block the tab when dispatching an intent until we're sure we're going to show a dialog.

BUG=144782
R=gbillock@chromium.org


Review URL: https://chromiumcodereview.appspot.com/10869062

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@153523 0039d316-1c4b-4281-b951-d872f2087c98
parent 59002090
......@@ -194,10 +194,6 @@ void WebIntentPickerController::SetIntentsDispatcher(
void WebIntentPickerController::ShowDialog(const string16& action,
const string16& type) {
// As soon as the dialog is requested, block all input events
// on the original tab.
tab_contents_->constrained_window_tab_helper()->BlockTabContent(true);
// Only show a picker once.
// TODO(gbillock): There's a hole potentially admitting multiple
// in-flight dispatches since we don't create the picker
......@@ -251,6 +247,9 @@ void WebIntentPickerController::ShowDialog(const string16& action,
}
}
// As soon as the dialog is requested, block all input events
// on the original tab.
tab_contents_->constrained_window_tab_helper()->BlockTabContent(true);
SetDialogState(kPickerSetup);
pending_async_count_++;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment