Reland "[conversions] Route impressions alongside rel="noopener" anchor navs"

This is a reland of 53e3903f456a5c3152a022c9a92ed99246a84ebd

This now correctly initializes the was_opener_suppressed_ member on
NavigationRequest.

Original change's description:
> [conversions] Route impressions alongside rel="noopener" anchor navs
>
> What:
> Route impressions for the Conversion Measurement API to the browser
> process for anchor tags with rel="noopener".
>
> Why:
> We currently drop impressions for anchor clicks which have noopener
> set because the impressions do not get forwarded to the browser process.
>
> Anchor click navigations with the rel="noopener" attribute use a
> different navigation path than those without the attribute, in which
> the window creation mojo also navigates the frame to the target url.
> This navigation is not annotated with an impression.
>
> How:
> Add an Impression member to CreateNewWindowParams which will get
> forwarded as a LoadURLParam for the subsequent navigation of the
> window.
>
> This change also fixes a bug in which initiator_frame_tokens are not
> set for noopener navigations.
>
> As of https://chromium-review.googlesource.com/c/chromium/src/+/2327963,
> the lack of an initiator frame tokens are used to to indicate whether
> an opener was suppressed for a navigation. Because attaching the token
> breaks this logic, we route a new |was_opener_suppressed| param through
> the NavigationController:LoadUrlWithParams() flow to recover the
> behavior.
>
> Bug: 1155577
> Change-Id: I84739a9f4ec0df9a867f91397f80b46eea1bcee6
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575223
> Commit-Queue: John Delaney <johnidel@chromium.org>
> Reviewed-by: Charlie Harrison <csharrison@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Charlie Reis <creis@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#838275}

Bug: 1155577
Change-Id: I1ab5bf85e62525e898bd9e9a6986ed844a7a5c39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2600016
Commit-Queue: John Delaney <johnidel@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#840653}
25 files changed
tree: 0002067b694ac0e4f9af97e7ae1ab72aa11a7fd2
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  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.