@page background painting.

In paginated layout, the document background (typically specified on the
BODY or HTML element) is painted on the page border box. Additionally,
@page rules may specify a background property, and this one is painted
over the entire page, including the margin area. This one is painted
before any document background.
See https://drafts.csswg.org/css-page-3/#painting

All document (fragmented) contents are painted by separate paint layers,
i.e. the layer established by the document root (HTML), in addition to
any other top layers. Page containers and border boxes, on the other
hand, do not establish layers, and are painted normally under the paint
layer of the LayoutView. When printing a page, have BoxFragmentPainter
look up the page container fragment of the current page, and paint just
that, with an infinite cull rect.

PhysicalFragment::IsPaginatedRoot() wasn't entirely correct, since it
would also return true for non-paginated documents, as long as we were
printing. Iframes, for instance, are not laid out for pagination, but
printed as-is. With the new callsites, these false positives would cause
trouble. Fix that, and move the function down to PhysicalBoxFragment, to
utilize IsFragmentationContextRoot().

Pre-paint now needs to visit page container and page border box
fragments, in order to set the paint offsets correctly.

Layout still doesn't set the correct offsets for the page border box
(margins are still handled on the outside of Blink), so for now, make
sure that the tests have zero margins.

Bug: 40286153
Change-Id: Ie4808491f1a570b9d223caeea3fa815995989703
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5522582
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1298373}
23 files changed
tree: cdb57724b072fb6c50e9309e010faf2ec69e4149
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  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. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  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.