[LayoutNG] Lay out OOFs in inner multicol during nested fragmentation

This CL is the first of several to add support for OOF layout in
a nested fragmentation context. To allow the OOF elements to get added
to the inner multicol rather than the outermost, a new builder
and constraint space are created for the inner multicol. Doing so also
allows us to re-use the existing OOF code with minimal effort.

Once the OOFs have been laid out and the new column fragments are
created, we need to replace the associated column fragments inside
the existing multicol fragment (instead of inside the builder itself).
In order to accomplish this, I've exposed a mutable accessor to the
children of a physical fragment.

A simple unit test was added to illustrate what is currently
working. It appears that the static position is not quite right yet,
and there is another related unit test that is hitting a DCHECK.
These will be addressed in follow-up changes, along with a few
other added TODOs (as well as additional testing).

Bug: 1079031
Change-Id: Ia529fd13b574797888deb19f7c5315eea6d9c906
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2674410
Commit-Queue: Alison Maher <almaher@microsoft.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852223}
8 files changed
tree: fb2e63fad8bea8d4821eaaf7773187b6903145f3
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. 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.