commit | fd9a6c73c9e331a8deb6ff6325d1c6fa5020bba6 | [log] [tgz] |
---|---|---|
author | Timothy Gu <timothygu@chromium.org> | Tue Dec 13 02:41:44 2022 |
committer | Chromium WPT Sync <blink-w3c-test-autoroller@chromium.org> | Tue Dec 13 02:41:44 2022 |
tree | b7e3747acf4dd01734f6e58be053218ba9ab3f04 | |
parent | eed89e3016c6fd9de02af8a9dcb06933244c54f9 [diff] |
url: limit number of slashes consumed after file: The file: URL parser currently unconditionally consumes all slashes after the file: scheme, leading to the following parses: file://////C:/abc -> file:///C:/abc file:/\/\/\foo/bar -> file:///foo/bar (on POSIX) However, the path canonicalizer does not behave consistently with this parsing behavior. When the path has . or .., the parser can output non-roundtrippable strings: file:///.//C:/abc -> file:////C:/abc -> file:///C:/abc One way to fix this is to make the canonicalizer strip the leading slashes after path normalization. However, the spec-compliant behavior is to maintain the number of leading slashes, so as to form the following: file:///.//C:/abc -> file:////C:/abc file://////C:/abc -> file://////C:/abc file:/\/\/\foo/bar -> file://////foo/bar (on POSIX) This CL aligns the behavior with Firefox and Safari. ~~~~~~ A few more necessary fixes are included in this CL. In particular, net::FilePathToFileURL() previously assumed that additionally slashes would get squashed, and was doing "file:///" + "/foo/bar.txt". While previously this would result in three slashes as expected, the same concatenation would now result in four slashes without code changes. Additionally on Windows, while previously file://///c| would get normalized to file:///C: by the URL parser, it is no longer the case. So net::FileURLToFilePath() would need to do the normalization itself. This CL adds many more test cases for file path<->URL conversion subroutines in order to prevent future regressions. Bug: 706335, 1130973, 1132533, 1132957 Change-Id: Ic2012215d234dd8490553d82c2ea859c8acc9d35
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:
wpt:matrix.org
matrix channel; includes participants located around the world, but busiest during the European working day.If 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.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.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 wpt.live and w3c-test.org.
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!