Fully implement bidi for a line's trailing spaces (UAX#9 L1)

Per UAX#9 L1, any spaces that after line breaking would fall logically
at the end of a line must be reset to the paragraph's initial
embedding level, regardless of the embedding level of those spaces in
the paragraph. Until now, Blink only had partial support for this.

The reason this was hard to implement in Blink is because the
direction of text is computed in a per-paragraph level, splitting the
text into items with a given direction and embedding level. Those
items are then split into item results when line breaking, but item
results must have the same direction as the item.

As part of line breaking, some item results are produced which only
have trailing spaces. The partial support, implemented in
crrev.com/c/2505486, consisted of marking these results with the
`has_only_trailing_spaces` flag, and using this flag to distinguish
them when reordering the item results.

This patch builds on top of that partial fix by adding a final
processing step to line breaking, which splits item results so that
trailing spaces (with a different embedding level as the paragraph)
are split into its own item result, and by marking all trailing spaces
item results as `has_only_trailing_spaces`.

This also fixes bug 1514753, where having a item result with non-base
direction which had logically trailing spaces was causing the text
(rather than the spaces) to hang, because
`LineInfo::ComputeTrailingSpaceWidth` assumed that UAX#9 L1 held.

This patch also modifies some existing WPT tests to make them use a
monospace Arabic webfont (since it's not guaranteed that all OS's have
one), and by changing the widths slightly to work around bug 1409445.

Bug: 316409, 1514753
Change-Id: I1eb751b457d413b5099dad8f95badba9a1b3e5fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5199988
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Andreu Botella <abotella@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1257309}
18 files changed
tree: b535f4a01a0f2ecda216978c70c9c38f9c898520
  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. DEPS
  71. DIR_METADATA
  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.