Migrate DeprecatedEqual to EqualASCII for HTML attribute values

DeprecatedEqualIgnoringCase (“DeprecatedEqual”) returns true iff the
two given strings are equal under non-Turkic case folding (full iff
both strings are 16-bit, simple otherwise).

DeprecatedEqual was deprecated in favour of EqualIgnoringASCIICase or
EqualIgnoringUnicodeCase [1]. The former is usually the appropriate
choice for web platform features that need to check for equality with
a constant keyword.

This CL migrates a significant subset of DeprecatedEqual calls: those
where one of the arguments is an 8-bit literal, containing only ASCII,
defined (or ought to be defined) somewhere in the HTML specification.

Unlike the last three patches against the same bug, these changes come
with web platform tests. This is because they’re author-facing and the
values contain the letter “s”, one of the four ASCII characters whose
equivalence class would change when switching from simple non-Turkic
case folding to ASCII insensitivity [2].

The engine changes are a curated subset of the following replacement
under Sublime Text 2 (PCRE):

Find:           (?x-i)
                (?<escape>\\['"?\\abfnrtv]){0}
                (?<literal>"(?:(?=[ -~])[^"]|(?&escape))*"){0}
                (?<any>(?:[^(),]|(\((?:[^()]*|(?-1))\)))*+){0}
                DeprecatedEqualIgnoringCase
                (\s*\(\s*+(?:
                    (?&literal)\s*,\s*+(?&any)
                    |(?&any)\s*,\s*+(?&literal)
                )\s*\))
Where:          *.cc,-/path/to/src/out/*,-/path/to/src/.clangd/*
Replace:        EqualIgnoringASCIICase$5

[1] https://codereview.chromium.org/2811793004/patch/1/10109
[2] https://www.unicode.org/Public/UCD/latest/ucd/CaseFolding.txt

Bug: 627682
Change-Id: I5f4279a3f6957d3604357df5da7c67ff2bdcdb1c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032655
Commit-Queue: Delan Azabani <dazabani@igalia.com>
Reviewed-by: Frédéric Wang <fwang@igalia.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750965}
33 files changed
tree: e2e2ab3b6d48cd77b930568e7b0aa2638303face
  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. largest-contentful-paint/
  88. layout-instability/
  89. lifecycle/
  90. loading/
  91. longtask-timing/
  92. magnetometer/
  93. mathml/
  94. measure-memory/
  95. media/
  96. media-capabilities/
  97. media-playback-quality/
  98. media-source/
  99. mediacapture-depth/
  100. mediacapture-fromelement/
  101. mediacapture-image/
  102. mediacapture-record/
  103. mediacapture-streams/
  104. mediasession/
  105. mimesniff/
  106. mixed-content/
  107. mst-content-hint/
  108. native-file-system/
  109. navigation-timing/
  110. netinfo/
  111. network-error-logging/
  112. notifications/
  113. offscreen-canvas/
  114. old-tests/
  115. orientation-event/
  116. orientation-sensor/
  117. origin-policy/
  118. page-visibility/
  119. paint-timing/
  120. payment-handler/
  121. payment-method-basic-card/
  122. payment-method-id/
  123. payment-request/
  124. performance-timeline/
  125. PeriodicBackgroundSync/
  126. permissions/
  127. permissions-request/
  128. permissions-revoke/
  129. picture-in-picture/
  130. pointerevents/
  131. pointerlock/
  132. portals/
  133. preload/
  134. presentation-api/
  135. printing/
  136. priority-hints/
  137. proximity/
  138. push-api/
  139. quirks/
  140. referrer-policy/
  141. remote-playback/
  142. reporting/
  143. requestidlecallback/
  144. resize-observer/
  145. resource-timing/
  146. resources/
  147. screen-capture/
  148. screen-orientation/
  149. screen_enumeration/
  150. scroll-animations/
  151. scroll-to-text-fragment/
  152. secure-contexts/
  153. selection/
  154. serial/
  155. server-timing/
  156. service-workers/
  157. shadow-dom/
  158. shape-detection/
  159. signed-exchange/
  160. speech-api/
  161. storage/
  162. storage-access-api/
  163. streams/
  164. subresource-integrity/
  165. svg/
  166. svg-aam/
  167. timing-entrytypes-registry/
  168. tools/
  169. touch-events/
  170. trust-tokens/
  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
  • 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.

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!