[Blink] Massage WebGL {Pre, Post}FinalizeFrame() flow

The objective here is to get the GetOrCreateCanvasResourceProvider()
calls and the PaintRenderingResultsToCanvas() call all directly next
to each other in HTMLCanvasElement::PostFinalizeFrame().
PreFinalizeFrame(), CanvasRenderingContext::FinalizeFrame(), and
PostFinalizeFrame() are all (and only called) directly in a row [1],
so this can be done by just moving the code to all be in
PostFinalizeFrame() in the same order as it is currently.

This unlocks followup refactoring of this flow to avoid having it talk
in terms of CanvasResourceProvider for low-latency WebGL.

Note: `did_print_current_task_`, which is cleared between the calls to
FinalizeFrame() and PostFinalizeFrame() [2], is not read in
PostFinalizeFrame(); outside of its read earlier in `DidProcessTask()`,
it is read only in a Canvas2D-specific method here [3].

[1] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/canvas/canvas_rendering_context.cc;l=108-118;drc=70343319512a4883095fdb100796ea70fba34b9e;bpv=1;bpt=1
[2] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/canvas/canvas_rendering_context.cc;l=115;drc=70343319512a4883095fdb100796ea70fba34b9e
[3] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/canvas/html_canvas_element.cc;l=380;drc=70343319512a4883095fdb100796ea70fba34b9e;bpv=1;bpt=1

Bug: 352263194
Change-Id: I57e85026367c11783edc9af796f0066c0013d69d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6592180
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1466330}
4 files changed
tree: 2020190ba58eb47066558b32735dcf794c450dfc
  1. .github/
  2. android_webview/
  3. apps/
  4. ash/
  5. base/
  6. build/
  7. build_overrides/
  8. buildtools/
  9. cc/
  10. chrome/
  11. chromecast/
  12. chromeos/
  13. codelabs/
  14. components/
  15. content/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  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. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. SECURITY_OWNERS
  80. 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.