[Gap Decorations]: Implement grid gap decorations for fragmentation

This CL begins the implementation of grid gap decorations for
fragmentation. To support fragmentation, row gaps that are either split
or are the last content in a fragmentainer HAVE to be suppressed [1].
This change addresses this by: (1) Modifying intrinsic block size item
offsets based on the delta of any gap that extends beyond the
fragmentainer (2) Excluding such gaps from the fragment relative gap
geometry.

The implementation details in this change involves recording the
original gap positions in a non-fragmented context, then "PlaceGaps"
uses this geometry during fragmentation. If a gap doesn't fit in the
current fragmentainer, the last placed gap is considered as a
suppression candidate. It is suppressed if it's the last content in the
fragmentainer or is split across multiple fragmentainers.

Test cases as wpts have been added to exercise this change. Future
changes will address spanning items and `rule-break` functionality in
fragmented grids, subgrid, and eventually add fragmentation support for
gap decorations in flex and multi-column layouts.

[1]: https://github.com/w3c/csswg-drafts/issues/11520

Bug: 357648037, 394042462
Change-Id: I4dd123cf9a59b4d70eedee61ae99ab2fe8de011a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6900436
Reviewed-by: Alison Maher <almaher@microsoft.com>
Commit-Queue: Sam Davis Omekara <samomekarajr@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1519628}
31 files changed
tree: bb4cf5d89c206b0254b060c067a3e35ce1c78056
  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.