Revert "Update AssistantBottomSheetContent back press handling to align with new back gesture API"

This reverts commit 31bb49a61cc4d15653a9c8eb3b9310d2dd974c49.

Reason for revert:  crbug.com/1344746

Original change's description:
> Update AssistantBottomSheetContent back press handling to align with new back gesture API
>
> This CL is a follow up to crrev.com/c/3669515 and includes refactoring of the AssistantBottomSheetContent back press handling implementation. AssistantBottomSheetContent#setHandleBackPress introduced in this CL determines and updates ahead-of-time back press handling behavior by the sheet content.
>
> There are three implementations of AssistantBottomBarDelegate#onBackButtonPressed that need to be accounted for.
>
> 1. In AssistantBottomBarNativeDelegate
> AssistantBottomBarNativeDelegate#onBackButtonPressed invokes the JNI method AssistantBottomBarNativeDelegate#onBackButtonClicked that always handles the back press except in case of the AutofillAssistantState::BROWSE state in UiControllerAndroid.
>
> 2. In AssistantTriggerScript
> AssistantTriggerScript.Delegate#onBackButtonPressed invokes the JNI method AssistantTriggerScriptBridge#onBackButtonPressed that always handles the back press when a trigger script is shown.
>
> 3. In BottomSheetOnboardingCoordinator
> Back press is always handled in this case.
>
> In addition to these updates, the CL moves the bottom sheet back press handler initialization from ChromeTabbedActivity to ChromeActivity.
>
> Bug: 1279941
> Change-Id: Iaa275b4751b0c306672d252d2414025dd7dd690f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3714965
> Reviewed-by: Clemens Arbesser <arbesser@google.com>
> Reviewed-by: Theresa Sullivan <twellington@chromium.org>
> Reviewed-by: Lijin Shen <lazzzis@google.com>
> Commit-Queue: Aishwarya Rajesh <aishwaryarj@google.com>
> Cr-Commit-Position: refs/heads/main@{#1024022}

Bug: 1279941,1344746
Change-Id: I18d7db8664abb0fa72df6b0fa5e6148f799686ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3765539
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Clemens Arbesser <arbesser@google.com>
Commit-Queue: Theresa Sullivan <twellington@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1024761}
11 files changed
tree: a160ae80f98704343ae72ba76c28a1a4ce152ff1
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.