Update NewTabPagePreloadPipeline*::StartPrerender behavior

This CL makes following changes similar to http://crrev.com/c/6857734
1. Introduce `NewTabPagePreloadPipelineManager::EnsurePipelineForUrl`
which resets pipeline if url mismatches in `StartPrerender`. This
guarantees a new pipeline or a pipeline with the same url.
2. Remove return value in `NewTabPagePreloadPipeline::StartPrerender`
as the pipeline manager will not reset pipeline according to the
trigger result anymore.
3. Due to mechanism in 1, if a `prerender_handle_` exists, it must
have the same url. Remove `prerender_handle_->IsValid()` from the
duplicate check condition in
`NewTabPagePreloadPipeline::StartPrerender`.

Behavioral change:
1. Before the changes
`NewTabPagePreloadPipelineManager::StartPrerender` returns if
pipeline is not null, now it creates a new pipeline if the given url
is different.
2. `NewTabPagePreloadPipelineManager::StartPrerender` no longer
resets pipeline according to the result of
`NewTabPagePreloadPipeline::StartPrerender`.
We expect that 2 doesn't affect user's experience. 1 changes the behavior for
two mouseenters that don't contain mouseleave, but it's quite rare and safe.

Bug: 421941586
Change-Id: I845f4fffc303672397be2d7dafcb240a16b3d275
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6865471
Commit-Queue: Huanpo Lin <robertlin@chromium.org>
Reviewed-by: Ken Okada <kenoss@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1506885}
4 files changed
tree: e09b5a6dea795ecc0d33cff8b92e4ba04ca265d2
  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.