Compute the NGLineInfo hang_width even if ignored in text alignment

The NGLineInfo class has an attribute hang_width_ to store the width
of the preserved trailing spaces. Theoretically, this value is intended
to be used during text alignment, following the rules discussed and
resolved in the CSS WG issue 3440 [1]. In this issue it's been
discussed how to handle end-of-line pre-wrap spaces, which may hang and
could affect the final result of the text alignment.

However, we also use the NGLineInfo's attribute to compute the line
box's inline size, as part of the NGInlineLayoutAlgorithm::CreateLine
logic. Since we ignore the hanging spaces when using 'center'
alignment, we don't compute it; this leads to an incorrect inline size
of the fist line in the test case described in the bug 782638, which
incorrectly overflows the box's fixed size, causing the scrollbar to be
activated when it shouldn't.

Since we always compute the hang_width now, we need to consider it also
in the case of RTL scenarios, where we were assuming it was ignored
depending on certain values of the text alignment. In order to avoid
regressions, this CL also simplifies the line_box's inline_size
computation performed in the CreateLine function, ignoring for now the
text direction, we always subtract the hang_width

Then, the inclusion or not of the hang_width will be decided where it
should; the function NGInlineLayoutAlgorithm::ApplyTextAlign is the one
responsible of implementing the rules agreed in the CSS WG issue
mentioned before.

https://github.com/w3c/csswg-drafts/issues/3440

Bug: 782638, 1278559
Change-Id: Ib1950533169fb9cabc6b7bb9e6925451eff2a767
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3360876
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Cr-Commit-Position: refs/heads/main@{#961084}
15 files changed
tree: 22a59fa60889f23634ab0b7370bdeccc2492305f
  1. .github/
  2. .well-known/
  3. accelerometer/
  4. accessibility/
  5. accname/
  6. acid/
  7. ambient-light/
  8. animation-worklet/
  9. annotation-model/
  10. annotation-protocol/
  11. annotation-vocab/
  12. apng/
  13. app-history/
  14. appmanifest/
  15. audio-output/
  16. background-fetch/
  17. BackgroundSync/
  18. badging/
  19. battery-status/
  20. beacon/
  21. bluetooth/
  22. clear-site-data/
  23. client-hints/
  24. clipboard-apis/
  25. common/
  26. compat/
  27. compression/
  28. compute-pressure/
  29. conformance-checkers/
  30. console/
  31. contacts/
  32. content-dpr/
  33. content-index/
  34. content-security-policy/
  35. contenteditable/
  36. cookie-store/
  37. cookies/
  38. core-aam/
  39. cors/
  40. credential-management/
  41. css/
  42. custom-elements/
  43. custom-state-pseudo-class/
  44. delegated-ink/
  45. density-size-correction/
  46. deprecation-reporting/
  47. device-memory/
  48. direct-sockets/
  49. docs/
  50. document-policy/
  51. dom/
  52. domparsing/
  53. domxpath/
  54. dpub-aam/
  55. dpub-aria/
  56. editing/
  57. element-timing/
  58. encoding/
  59. encoding-detection/
  60. encrypted-media/
  61. entries-api/
  62. event-timing/
  63. eventsource/
  64. eyedropper/
  65. feature-policy/
  66. fetch/
  67. file-system-access/
  68. FileAPI/
  69. focus/
  70. font-access/
  71. fonts/
  72. forced-colors-mode/
  73. fullscreen/
  74. gamepad/
  75. generic-sensor/
  76. geolocation-API/
  77. geolocation-sensor/
  78. graphics-aam/
  79. gyroscope/
  80. hr-time/
  81. html/
  82. html-longdesc/
  83. html-media-capture/
  84. idle-detection/
  85. imagebitmap-renderingcontext/
  86. images/
  87. import-maps/
  88. IndexedDB/
  89. inert/
  90. infrastructure/
  91. input-device-capabilities/
  92. input-events/
  93. installedapp/
  94. interfaces/
  95. intersection-observer/
  96. intervention-reporting/
  97. is-input-pending/
  98. js/
  99. js-self-profiling/
  100. keyboard-lock/
  101. keyboard-map/
  102. largest-contentful-paint/
  103. layout-instability/
  104. lifecycle/
  105. loading/
  106. longtask-timing/
  107. magnetometer/
  108. managed/
  109. mathml/
  110. measure-memory/
  111. media/
  112. media-capabilities/
  113. media-playback-quality/
  114. media-source/
  115. mediacapture-depth/
  116. mediacapture-fromelement/
  117. mediacapture-image/
  118. mediacapture-insertable-streams/
  119. mediacapture-record/
  120. mediacapture-streams/
  121. mediasession/
  122. merchant-validation/
  123. mimesniff/
  124. mixed-content/
  125. mst-content-hint/
  126. native-io/
  127. navigation-timing/
  128. netinfo/
  129. network-error-logging/
  130. notifications/
  131. old-tests/
  132. orientation-event/
  133. orientation-sensor/
  134. origin-policy/
  135. page-lifecycle/
  136. page-visibility/
  137. paint-timing/
  138. parakeet/
  139. payment-handler/
  140. payment-method-basic-card/
  141. payment-method-id/
  142. payment-request/
  143. performance-timeline/
  144. periodic-background-sync/
  145. permissions/
  146. permissions-policy/
  147. permissions-request/
  148. permissions-revoke/
  149. picture-in-picture/
  150. pointerevents/
  151. pointerlock/
  152. portals/
  153. preload/
  154. presentation-api/
  155. priority-hints/
  156. private-click-measurement/
  157. proximity/
  158. push-api/
  159. quirks/
  160. referrer-policy/
  161. remote-playback/
  162. reporting/
  163. requestidlecallback/
  164. resize-observer/
  165. resource-timing/
  166. resources/
  167. sanitizer-api/
  168. savedata/
  169. scheduler/
  170. screen-capture/
  171. screen-orientation/
  172. screen-wake-lock/
  173. screen_enumeration/
  174. scroll-animations/
  175. scroll-to-text-fragment/
  176. secure-contexts/
  177. secure-payment-confirmation/
  178. selection/
  179. serial/
  180. server-timing/
  181. service-workers/
  182. shadow-dom/
  183. shape-detection/
  184. signed-exchange/
  185. speculation-rules/
  186. speech-api/
  187. storage/
  188. storage-access-api/
  189. streams/
  190. subresource-integrity/
  191. svg/
  192. svg-aam/
  193. timing-entrytypes-registry/
  194. tools/
  195. touch-events/
  196. trust-tokens/
  197. trusted-types/
  198. ua-client-hints/
  199. uievents/
  200. upgrade-insecure-requests/
  201. url/
  202. urlpattern/
  203. user-timing/
  204. vibration/
  205. video-rvfc/
  206. virtual-keyboard/
  207. visual-viewport/
  208. wai-aria/
  209. wasm/
  210. web-animations/
  211. web-bundle/
  212. web-locks/
  213. web-nfc/
  214. web-otp/
  215. web-share/
  216. webaudio/
  217. webauthn/
  218. webcodecs/
  219. WebCryptoAPI/
  220. webdriver/
  221. webgl/
  222. webgpu/
  223. webhid/
  224. webidl/
  225. webmessaging/
  226. webmidi/
  227. webnn/
  228. webrtc/
  229. webrtc-encoded-transform/
  230. webrtc-extensions/
  231. webrtc-ice/
  232. webrtc-identity/
  233. webrtc-priority/
  234. webrtc-stats/
  235. webrtc-svc/
  236. websockets/
  237. webstorage/
  238. webtransport/
  239. webusb/
  240. webvr/
  241. webvtt/
  242. webxr/
  243. workers/
  244. worklets/
  245. x-frame-options/
  246. xhr/
  247. xslt/
  248. .azure-pipelines.yml
  249. .gitattributes
  250. .gitignore
  251. .mailmap
  252. .taskcluster.yml
  253. CODE_OF_CONDUCT.md
  254. CODEOWNERS
  255. CONTRIBUTING.md
  256. LICENSE.md
  257. lint.ignore
  258. README.md
  259. testharness_runner.html
  260. wpt
  261. wpt.py
README.md

The web-platform-tests Project

Taskcluster CI Status documentation manifest Python 3

The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.

The most important sources of information and activity are:

  • github.com/web-platform-tests/wpt: the canonical location of the project's source code revision history and the discussion forum for changes to the code
  • web-platform-tests.org: the documentation website; details how to set up the project, how to write tests, how to give and receive peer review, how to serve as an administrator, and more
  • wpt.live: a public deployment of the test suite, allowing anyone to run the tests by visiting from an Internet-enabled browser of their choice
  • wpt.fyi: an archive of test results collected from an array of web browsers on a regular basis
  • Real-time chat room: the wpt:matrix.org matrix channel; includes participants located around the world, but busiest during the European working day.
  • Mailing list: a public and low-traffic discussion list
  • RFCs: a repo for requesting comments on substantial changes that would impact other stakeholders or users; people who work on WPT infra are encouraged to watch the repo.

If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.

Setting Up the Repo

Clone or otherwise get https://github.com/web-platform-tests/wpt.

Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune (or git fetch -p && git merge).

Running the Tests

See the documentation website and in particular the system setup for running tests locally.

Command Line Tools

The wpt command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:

  • wpt serve - For starting the wpt http server
  • wpt run - For running tests in a browser
  • wpt lint - For running the lint against all tests
  • wpt manifest - For updating or generating a MANIFEST.json test manifest
  • wpt install - For installing the latest release of a browser or webdriver server on the local machine.
  • wpt serve-wave - For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.

Windows Notes

On Windows wpt commands must be prefixed with python or the path to the python binary (if python is not in your %PATH%).

python wpt [command]

Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt commands.

Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false in your working tree.

Publication

The master branch is automatically synced to wpt.live and w3c-test.org.

Contributing

Save the Web, Write Some Tests!

Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.

The way to contribute is just as usual:

  • Fork this repository (and make sure you're still relatively in sync with it if you forked a while ago).
  • Create a branch for your changes: git checkout -b topic.
  • Make your changes.
  • Run ./wpt lint as described above.
  • Commit locally and push that to your repo.
  • Create a pull request based on the above.

Issues with web-platform-tests

If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!