[Clank Nav Cap] Top-level navigation from PWA to itself CUJ update

This CL implements a new navigation CUJ for Clank.

New behavior:

A new top level browsing context navigation (target="_blank" with no
additional modifier) starting in PWA task named A and towards a link in
scope of PWA A itself, should always cause a new task to be created even
if existing ones are available.

Background:

This is a specific behavior implemented in Desktop Chrome, where the
Launch Handler API is supported. This API provides customizable opening
logic for PWAs using the client_mode attribute.

Clank should already be supporting Launch Handler for Trusted Web
Activities from v138 (behind flag).

client_mode (a web app manifest.json attribute) defines 3 possible
policies for PWA opening:
- focus_existing: if a task is already open, focus it and do not navigate
- navigate_existing: if a task is already open, focus and navigate
- navigate_new: always open a new task, regardless of pre-existing ones

For PWA to itself navigations in new top-level browsing context
specifically, an edge case is applied on top of the API specification.
Instead of following the client_mode logic, a new task should be opened
every time.

Bug: 382776297
Change-Id: Ie430e17323877c1d4b3d5871ebc7620319219206
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6519655
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Fabio Muratori <muratori@google.com>
Cr-Commit-Position: refs/heads/main@{#1506188}
9 files changed
tree: 9d0e34558986133faf33c6caa6cbb1a4adffa5cd
  1. .gemini/
  2. .github/
  3. agents/
  4. android_webview/
  5. apps/
  6. ash/
  7. base/
  8. build/
  9. build_overrides/
  10. buildtools/
  11. cc/
  12. chrome/
  13. chromecast/
  14. chromeos/
  15. codelabs/
  16. components/
  17. content/
  18. crypto/
  19. dbus/
  20. device/
  21. docs/
  22. extensions/
  23. fuchsia_web/
  24. gin/
  25. google_apis/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. net/
  34. pdf/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .cursorignore
  54. .geminiignore
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. CRYPTO_OWNERS
  72. DEPS
  73. DIR_METADATA
  74. LICENSE
  75. LICENSE.chromium_os
  76. OWNERS
  77. PRESUBMIT.py
  78. PRESUBMIT_test.py
  79. PRESUBMIT_test_mocks.py
  80. README.md
  81. SECURITY_OWNERS
  82. 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.