[line-clamp] [RubyLB] Make sure ruby isn't visible in clamped lines

With RubyLB, in some cases ruby annotations would not be hidden even
though the line containing them would be. This is because when a line
is after the clamp point, the line box and its logical line items
would be marked as hidden for paint, but in RubyLB the line's ruby
annotations and their line items are stored in the logical ruby
columns.

This patch fixes this in `FragmentItemsBuilder::AddLine`, when
`FragmentItem`s are created for a line's multiple annotations, by
marking every item in the annotations as hidden for paint if the
line's fragment is marked as such.

Aside from adding a test for this issue, this patch also adds a test
that the sizing of a clamped block box properly takes into account any
ruby annotations that add leading to a line. This already worked as
expected, presumably due to https://crrev.com/c/5683304 storing the
`PreviousInflowPosition` at the clamp point, but the effect on ruby
had not been tested in that CL.

Bug: 40336192
Change-Id: I95fe796bb887d1d205dd43c2644095b6c6f225e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5695646
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Andreu Botella <abotella@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1326551}
6 files changed
tree: 2309d3a11bb0e2b2b2fb22c0acc86c2078d1468b
  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.