commit 037c445222ea3f11b51d689819485a1de78c9361
author Sayed Elabady <elabadysayed@chromium.org> Tue Oct 25 10:48:47 2022
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Tue Oct 25 10:48:47 2022
tree 01913acc3dddc62e304586729a6666c34541ab02
parent 89f6b82098c18e6925a86963b4af19270e0476cd

[Webview/BackNavigation]: Deprecate KEYCODE_BACK on T+

Starting from T apps should move away from KEYCODE_BACK and
go toward Predictive Back navigation, we need to add a flag to
the manifest to opt-in in the new way.

Webview's manifest is the host manifest so the developer should add
the flag to opt-in.

That's why I didn't add the sdk check in the `dispatchKeyEvent` as
the developer may not add the flag so we fallback to the old way.
shanh@ confirmed that only one of the two will be triggered
Keycode_back OR the callback


Bug: 1355965
Change-Id: Ie0c36ff716996d2e77dbfab57591aaef994df91f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3884416
Reviewed-by: Peter Conn <peconn@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Sam Maier <smaier@chromium.org>
Commit-Queue: Peter Conn <peconn@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1063231}