Launch an external app when Chrome cannot handle the URL

Launch an external app when Chrome cannot handle the URL

When some third-party app launched Chrome with an intent, and the URL
got redirected to another, we try to stay in Chroem unless there is a new
intent handler after redirection. The rationale here is that the user has
explicitly chosen Chrome over other intent handlers already, and we do not
want to bother them any more.

However, if the new URL is actually an external protocol, then Chrome
cannot handle it anyways. This CL fixes stay-in-Chrome logic and adds a
test case.

BUG=598546
Committed: https://crrev.com/54b7bc3dea8ab099971559538b9ffc50c79f6d8e
Cr-Commit-Position: refs/heads/master@{#385350}

[Changwan Ryu, 2016-04-04 02:43:11]

changwan@chromium.org changed reviewers:
+ tedchoc@chromium.org

[Ted C, 2016-04-05 16:31:26]

lgtm

[Changwan Ryu, 2016-04-05 23:55:18]

The CQ bit was checked by changwan@chromium.org

[commit-bot: I haz the power, 2016-04-05 23:55:47]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1855853002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1855853002/1

[commit-bot: I haz the power, 2016-04-06 00:38:57]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-06 00:39:53]

Description was changed from

==========
Launch an external app when Chrome cannot handle the URL

When some third-party app launched Chrome with an intent, and the URL
got redirected to another, we try to stay in Chroem unless there is a new
intent handler after redirection. The rationale here is that the user has
explicitly chosen Chrome over other intent handlers already, and we do not
want to bother them any more.

However, if the new URL is actually an external protocol, then Chrome
cannot handle it anyways. This CL fixes stay-in-Chrome logic and adds a
test case.

BUG=598546
==========

to

==========
Launch an external app when Chrome cannot handle the URL

When some third-party app launched Chrome with an intent, and the URL
got redirected to another, we try to stay in Chroem unless there is a new
intent handler after redirection. The rationale here is that the user has
explicitly chosen Chrome over other intent handlers already, and we do not
want to bother them any more.

However, if the new URL is actually an external protocol, then Chrome
cannot handle it anyways. This CL fixes stay-in-Chrome logic and adds a
test case.

BUG=598546

Committed: https://crrev.com/54b7bc3dea8ab099971559538b9ffc50c79f6d8e
Cr-Commit-Position: refs/heads/master@{#385350}
==========

[commit-bot: I haz the power, 2016-04-06 00:39:54]

Patchset 1 (id:??) landed as
https://crrev.com/54b7bc3dea8ab099971559538b9ffc50c79f6d8e
Cr-Commit-Position: refs/heads/master@{#385350}