[TG Sync] Identify sync initiated navigation using NavigationUiData

A navigation in response to a sync message is always filtered out
from sending back to sync in order to avoid ping pong issues.
Currently these sync initiated navigations are identified by
explicitly keeping the NavigationHandle pointer in
SavedTabGroupWebContentsListener.
This is cumbersome and requires a plumbing between the callsites
for LoadURL and the observer method DidFinishNavigation which is very
easy to miss.
This CL improves that by introducing a boolean in the NavigationHandle's
custom data (ChromeNavigationUiData). By setting this boolean
correctly and checking on the observer event, we get rid of the problem
of plumbing/managing NavigationHandles.
The boolean can be set at the NavigateParams (chrome layer) during
loading a URL which is then subsequently passed to NavigationUIData and
thereby being accessible from NavigationHandle.

Notes:
1. Manual testing - Manually verified three cases that this works
a. Navigating a tab on remote computer
b. Adding a new tab on remote computer
c. Opening a tab group from bookmarks bar
d. Navigating a local tab
e. Adding a local tab
f. Restarting chrome with the group/tab open

2. There is still plumbing of NavigationHandle pointers from several
callsites to the SavedTabGroupWebContentsListener class which isn't
required any more. Those will be removed soon in a follow-up CL.

3. This is still desktop only. As part of future work,
we aim to extend this support for android which requires a bit more plumbing and serialization to/from WebContentsState byte buffer.

Bug: 359982911
Change-Id: Ife9412122760a59893208275fdaf8cac78054f52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5980260
Reviewed-by: David Pennington <dpenning@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Darryl James <dljames@chromium.org>
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1376652}
8 files changed
tree: 0572888af163430604db7d8170d708b6c8f2a39b
  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. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.