[css-pseudo] Fix legacy ::marker margins not getting updated

Outside markers behave out-of-flowish, so their intrinsic contribution
to the list item should be 0.

In legacy, this is done by adding negative margins, so that the width of
the marker plus its margins are 0.

However, when calculating the intrinsic contributions of the children,
the code uses the margins in the computed style, not the margins of the
box. Therefore, the marker code used to replace the computed style with
another one that had the changed margins.

This approach was error-prone, for example special care was needed to
reapply the previously calculated margins when the computed style
changed, in order to avoid triggering unnecessary layout.

However, this caused a problem: if 'list-style-position' changed, the
old margins were preserved. But the margins depend on whether the marker
is inside or outside!

This patch fixes the problem and stops changing the computed style of
the marker.

For inside markers, margins don't depend on the size of the marker, and
they were already applied to the computed style in style_adjuster.cc, so
they work well. For outside markers, the patch skips them when
calculating the intrinsic size of the list item.

Bug: 1048672, 457718

TEST=external/wpt/css/css-pseudo/marker-intrinsic-contribution-001.html
TEST=external/wpt/css/css-pseudo/marker-intrinsic-contribution-002.html

The former test fails in LayoutNG because trailing marker spaces are not
preserved, and fails in legacy due to the lack of 'content' support.

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

The web-platform-tests Project

Taskcluster CI Status

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 IRC chat room named #testing on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived here
  • Mailing list: a public and low-traffic discussion list

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.

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 http://w3c-test.org/.

Pull requests are automatically mirrored except those that modify sensitive resources (such as .py). The latter require someone with merge access to comment with “LGTM” or “w3c-test:mirror” to indicate the pull request has been checked.

Branches

In the vast majority of cases the only upstream branch that you should need to care about is master. If you see other branches in the repository, you can generally safely ignore them.

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!