GitLab

Currently navigations triggered from the embedder use a
navigation type of LINK. LINK navigations (mostly) result in
processing intents. This is not always desirable (for example,
the SRP shouldn't trigger intents).

This patch adds the ability to disable Intent processing.
I went with a function to disable vs an explicit setter as I
don't think we need support for an absolute 'true' case. By
that I mean if I did add a function like
setIntentProcessingEnabled(boolean value), the implication
is 'true' means intent processing always happens. In code that
isn't the case though, for example, a same host navigation may
not trigger intent resolution. As we don't need the ability
to force intent processing, I'm avoiding it for now.

BUG=1119365
TEST=covered by android tests

Change-Id: Ib374c1d61ce0795654a677b1ff29128f39c75bd9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369516Reviewed-by: Darin Fisher <darin@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801837}