commit | 4d00984a61358a8c3a743f60cb49ccc1ccffeae4 | [log] [tgz] |
---|---|---|
author | Delan Azabani <dazabani@igalia.com> | Tue Mar 17 15:29:43 2020 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Tue Mar 17 16:00:54 2020 |
tree | e2e2ab3b6d48cd77b930568e7b0aa2638303face | |
parent | d10a20b00ebdc75b0afe454b9e6300f41f6cf169 [diff] |
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}
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:
#testing
on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived hereIf you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
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
).
See the documentation website and in particular the system setup for running tests locally.
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 serverwpt run
- For running tests in a browserwpt lint
- For running the lint against all testswpt manifest
- For updating or generating a MANIFEST.json
test manifestwpt install
- For installing the latest release of a browser or webdriver server on the local machine.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.
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.
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.
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:
git checkout -b topic
../wpt lint
as described above.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!