[FlexNG] GiveItemsFinalPositionAndSizeForFragmentation

Refactor GiveItemsFinalPositionAndSize() such that the fragmentation
specific logic is moved into a new method called
GiveItemsFinalPositionAndSizeForFragmentation(). With this update, we
will end up looping over items twice in the first fragmentainer - once
with the initial call to GiveItemsFinalPositionAndSize(), and second
when GiveItemsFinalPositionAndSizeForFragmentation() is called. In
subsequent fragmentainers, only the latter will be called.

The main reason that we call GiveItemsFinalPositionAndSize() initially
in the case of fragmentation is that only a subset of item information
is stored in between fragmentainers, so certain info needs to be
propagated for all items before moving on to the next fragmentainer.
This propagation will only happen in GiveItemsFinalPositionAndSize().

We will also need to know the original block-size of an item in order
to tell if an item has expanded due to fragmentation. The plan will be
to store this on the NGFlexItem in a follow-up change. This info will
be set on the item in GiveItemsFinalPositionAndSize(), at which point
we will know the non-fragmented block-size of all items (including
stretched items).

A couple of things to point out:
- GiveItemsFinalPositionAndSize() no longer uses the NGFlexItemIterator,
since we do not need to make various fragmentation related checks in
that method while looping.
- Since buttons and sliders are not fragmentable, only adjust the
baselines for those in GiveItemsFinalPositionAndSize().

This CL should not result in any functional change.

Bug: 660611
Change-Id: I2a4acf7981a658e45958f59a3579d7d6405f2100
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3288786
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#943269}
2 files changed
tree: 03b44b4278e887e44aae28caa6ced6cf2ef4492f
  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. .mailmap
  61. .rustfmt.toml
  62. .vpython
  63. .vpython3
  64. .yapfignore
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. DEPS
  70. DIR_METADATA
  71. ENG_REVIEW_OWNERS
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. 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.