[anchor] Update OOF style correctly when nothing fits

We currently have a bug when updating the OOF style for an element
that:

 * Does not contain any anchor*() functions (or similar).
 * Has an overflowing base style.
 * Has at least one item in position-try-options, all of which overflow.

In the above case, neither the base attempt nor the position-try-option
attempts are successfully placed within the CB, and during OOF style
iteration (OOFCandidateStyleIterator) we then go back to the base
styles. The problem is that this we'll then call UpdateStyleForOutOfFlow
with try_set=nullptr and tactic_list=<empty>, which (absent any anchor()
queries) causes the current logic to think that no update is needed.
However, the ComputedStyle currently held by the element is the style
from the last (failed) position-try attempt, so an update *is* needed
if we want to back to base.

To fix this:

 * A call to UpdateStyleForOutOfFlow is now unconditional.
   It will always recalculate the style.
 * When OOFCandidateStyleIterator is initialized, we check if
   we depend on anchor*() queries, and if so update the style.
   This initialization is reached by all OOFs, not just those that
   use anchor positioning features.
 * All other calls to UpdateStyle in OOFCandidateStyleIterator
   will always lead to a style recalc. That's because these calls only
   take place when there's some position-try-option being processed,
   which are exactly the cases where we always need to recalc the style.

Fixed: 339686368
Change-Id: I046e20527e29924d8b6fbbd794232f51b7a2bb59
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5616572
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1313301}
4 files changed
tree: 91f3d5d1b28d0deb48060ab2441df69577611c93
  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.