[Blink] Change HTMLCanvasPainter test setup

The test invokes CanvasRenderingContext2D::FinalizeFrame() after first
setting up HTMLCanvasElement to have a non-null Canvas2DLayerBridge
(via the SetResourceProviderForTesting() call) to ensure that
CanvasRenderingContext2D regards the canvas as paintable and doesn't
short-circuit out. However, we will shortly be changing
CanvasRenderingContext2D::IsPaintable() to check for the presence of
the CanvasResourceProvider rather than the bridge. In preparation, this
CL changes this test's setup to create the CanvasResourceProvider rather
than just the bridge.

Note that the new test setup is more representative of a production flow
in any case:

* In production the only way for the bridge to be created is via
  an attempt to create the provider, so that must have been invoked
  before FinalizeFrame() for FinalizeFrame() to regard the canvas as
  paintable
* While it is possible for GetOrCreateCanvasResourceProvider() to
  successfully create the bridge and fail to create the provider, if
  FinalizeFrame() is called after that occurs it will also fail to
  create the provider and will short-circuit out here [1].

[1] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/canvas/canvas2d/canvas_rendering_context_2d.cc;l=848-850?q=CanvasRenderingContext2D::FinalizeFra&ss=chromium

Bug: 40280152
Change-Id: Ic06c18246f623f4a7b8f429a6d8b1a983aa22828
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6233993
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Jean-Philippe Gravel <jpgravel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1416655}
1 file changed
tree: 08c3fe378a78e59f4ebde46cc9e1140ade2e87ee
  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.